# Globalize and SQL Server **URL:** \ **Category:** Rails\ **Created:** [April 20, 2007, 2:12pm UTC](https://www.ruby-forum.com/t/globalize-and-sql-server/92536 "2007-04-20T14:12:49Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\ **Post date:** [April 20, 2007, 2:12pm UTC](https://www.ruby-forum.com/t/globalize-and-sql-server/92536/1 "2007-04-20T14:12:49Z")
Hello, At my work we have a lot of international clients and i10n is a big issue. We’re now planning to migrate our main application to ruby on rails. The problem is that we still have to use MS SQL Server because this is a selling point to big clients (don’t ask why) and Globalize doesn’t support this. My question is if anyone knows of a way to get around this? - is it possible (and not too hard) to write our own ms sql layer for globalize? - can something be done using odbc? - or is it possible for Globalize to connect to a separate server ( e.g. mysql)? Many thanks in advance, this would really help us out. ---
**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\ **Post date:** [April 20, 2007, 3:21pm UTC](https://www.ruby-forum.com/t/globalize-and-sql-server/92536/2 "2007-04-20T15:21:56Z")
On 20/04/07, removed\_email\_address@domain.invalid [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > My question is if anyone knows of a way to get around this? > > - is it possible (and not too hard) to write our own ms sql layer for > globalize? > - can something be done using odbc? > - or is it possible for Globalize to connect to a separate server > ( e.g. mysql)? I’m not sure why Globalize doesn’t support SQL Server - have you actually tried getting it to run? I’ve had a quick look at the code and can’t see any database dependent features being used anywhere. My advice would be create a dummy app and try it against SQL Server. It may well work without modification. If it doesn’t, you could either patch it yourself, or maybe use SQLite to store your localizations. Tom ---
**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\ **Post date:** [April 20, 2007, 5:28pm UTC](https://www.ruby-forum.com/t/globalize-and-sql-server/92536/3 "2007-04-20T17:28:26Z")
Yeah sorry my bad. The features page on Globalize ([http://www.globalize-rails.org/](http://www.globalize-rails.org/) globalize/show/Features#overview) says: “Databases \* Supports PostgreSQL, MySQL and Sqlite3 And, it’s ridiculously easy to add to your app.” Therefore i thought it wouldn’t support SQL Server. Meanwhile i’ve already contacted Sven F. of the Globalize team who quickly gave me an excellent response: … “Of the top of my head I’d say: Globalize is nothing but a plugin to Ruby on Rails. RoR itself should be able to cope with MS SQL Server I guess (e.g. see [1]). Thus, there should be no problem to use Globalize with MS SQL Server as well.” … “Your question regarding a custom MS SQL layer for Globalize is really the question if ActiveRecord (i.e. RoR) supports MS SQL and if there are any serious limitations. (Unfortunately I’m really not qualified to answer this question. I’d love to learn about this though as well as help with possible solutions of any problems.)” … So it will probably support MS SQL Server. I will let you know if things worked out. Thanks, Ben