Comments on: Connecting to MS SQL Server from Python on Mac OS X Leopard

By: 2kan

2kan — Thu, 21 Jan 2010 21:54:57 +0000

@Ed Singleton

I've just finished this project and switched back to web-development where i love RoR more then other frameworks. Also i like Rails & Ruby syntax more then Python. Ruby sugar makes program clean and readable, IMHO.

For most tasks Python and Ruby are similar except embedding of course. And threads %) And unicode (i wanna kill Ruby 1.9 developers and gonna use patch to force utf-8 everywhere it is possible).

By: Ed Singleton

Ed Singleton — Thu, 21 Jan 2010 16:42:41 +0000

@2kan

I found Linux easier to get working than Mac, so a Debian VM on your workstation is a workable idea. Particularly if it is a headless machine, and you ssh in.

And certainly moving to Postgres from MSSQL is vastly preferable to continuing to work with MSSQL. You're much luckier than me. I have to continue to work with legacy systems that are out of my control.

Out of interest, did you find Ruby easier than Python for this stuff, or did you only use Python for the transition?

By: 2kan

2kan — Thu, 21 Jan 2010 15:35:26 +0000

2 jeff I haven't reached success in connecting to MSSQL form SQLAlchemy from my mac. So I just created VS on my local linux office server where i easily setuped the environment. I had а task to migrate from MSSQL to Postgres so i've done the job on the server and continued developing on my mac %)

And right now i switched back to ruby from python %)

By: Ed Singleton

Ed Singleton — Thu, 21 Jan 2010 11:16:56 +0000

As I said above, it turns out that you do want to allow pyodbc to use iodbc. This process appears to configure both of them (or at least they both read their config from the same place).

Does isql my_dsn username password work for you? If not, your config is wrong. If it does work, then I’m a bit stumped. I’ve only had one oppurtunity to get it working so far, and haven’t been able to test my assumptions.

If you do get it working, please let me know what you did. (And if you get really stumped, feel free to email me, singletoned@gmail.com)

By: jeff

jeff — Thu, 21 Jan 2010 10:34:26 +0000

thanks for you article,I almost make it work on my mac! the isql works fine now,but i have the same problem as Timothy's. When try to get data from mssql server from SQLAlchemy: DBAPIError: (Error) (’IM002′, ‘[IM002] [iODBC][Driver Manager]Data source name not found and no default driver specified.

I try to add [Default] Driver = /opt/local/lib/libtdsodbc.so to your odbc.ini, and it should work.

but it doesn't work.

I found that the pyodbc use the iodbc instead unixODBC,how to switch them?

thank you again.

By: Nanda

Nanda — Tue, 12 Jan 2010 04:55:36 +0000

worked perfectly. thanks!

By: Ed Singleton

Ed Singleton — Wed, 12 Aug 2009 15:09:44 +0000

You're right. Having recreated the error message, it turns out I'm using iODBC as well (the default on Mac).

The error message means you need to add:

[Default]
Driver = /opt/local/lib/libtdsodbc.so

to your odbc.ini, and it should work.

Thanks for that. I'll update the article this evening.

By: Timothy Tsvetkov

Timothy Tsvetkov — Wed, 12 Aug 2009 14:21:48 +0000

Cool article. But i have a problem, when i try to get data from mssql server from SQLAlchemy:

DBAPIError: (Error) ('IM002', '[IM002] [iODBC][Driver Manager]Data source name not found and no default driver specified.

So, how to tell it to use unixODBC instead of not configured iODBC

Thx.