# Ruby 1.9, Rails 2.3.2, and MSSQL issue

**URL:** <https://www.ruby-forum.com/t/ruby-1-9-rails-2-3-2-and-mssql-issue/164610>\
**Category:** Rails\
**Created:** [April 3, 2009, 1:38am UTC](https://www.ruby-forum.com/t/ruby-1-9-rails-2-3-2-and-mssql-issue/164610 "2009-04-03T01:38:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![btomlin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/65b543/32.png) [@btomlin](https://www.ruby-forum.com/u/btomlin)\
**Post date:** [April 3, 2009, 1:38am UTC](https://www.ruby-forum.com/t/ruby-1-9-rails-2-3-2-and-mssql-issue/164610/1 "2009-04-03T01:38:40Z")

</div>

I am having a strange issue. I have upgraded to ruby 1.9.1 to do some  
testing on one of my machines. My app accesses a MSSQL database to  
pull in some information. Everything worked fine with ruby 1.8.6, but  
now if I try to navigate to a page that accesses that database I get  
this error:

DBI::InterfaceError in PagesController#company  
Unable to load driver ‘ODBC’ (underlying error: uninitialized constant  
DBI::DBD::ODBC)

I’m using activerecord-sqlserver-adapter (1.0.0.9250), dbd-odbc  
(0.2.4), and dbi (0.4.1)

---

<div class="post-metadata">

**Author:** ![btomlin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/65b543/32.png) [@btomlin](https://www.ruby-forum.com/u/btomlin)\
**Post date:** [April 3, 2009, 2:23am UTC](https://www.ruby-forum.com/t/ruby-1-9-rails-2-3-2-and-mssql-issue/164610/2 "2009-04-03T02:23:08Z")

</div>

I would say not all gems are mature for 191! Am I wrong?

---

<div class="post-metadata">

**Author:** ![btomlin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/65b543/32.png) [@btomlin](https://www.ruby-forum.com/u/btomlin)\
**Post date:** [April 3, 2009, 3:25am UTC](https://www.ruby-forum.com/t/ruby-1-9-rails-2-3-2-and-mssql-issue/164610/3 "2009-04-03T03:25:50Z")

</div>

You are right. The reason I posted this was because it was working  
using script/console, which would have meant the gems were all working  
with 1.9.1, but not when navigating to the page on the site. Then I  
realized that I was still running irb under ruby 1.8.6. Once I  
updated that to 1.9.1 it quit working. So yes it appears to be the  
gems are incompatible with 1.9.1.