E. James, that's a bummer because I have a bunch of legacy and current MSSQL data that I hoped to one day integrate with my newer Rails/MySQL based application. I saw the mention of MSSQL support in the Agile book so I figured I'd just cross that bridge when I got to it. Hmm, financial systems and such that are actively in use so I can't migrate them to MySQL. I may have to just end up just having to use triggers, DTS or something to move changes on the MSSQL server to MySQL.
Ah well, I guess I'll still cross that bridge when I get to it! :)
I had a client a year ago who demanded that the database be on MSSQL. I used to do a lot of .Net so I didn't care much.
However it turned into a nightmare due to dropped socket calls and driver problems.
I would seriously recommend using mysql as the main database and then using replication or something similar to move data to and from the rails database to any legacy mssql databased you have.
Well, I've got a couple of massive MSSQL databases here but my Rails apps are connecting to a MySql database. This page details connecting from Rails 1.x or 2.x as well as pointing out some gotchas. http://wiki.rubyonrails.org/rails/pages/HowtoConnectToMicrosoftSQLServer. I can successfully connect from my development app on my Windows workstation.
If your app is running on a Linux server then maybe this article will help with the missing pieces on there: http://wiki.rubyonrails.org/rails/pages/HowtoConnectToMicrosoftSQLServerFromRailsOnLinux