What's a good way to interface Python running on OS X with a cloud-based SQL Server database?

EDIT:

With pyodbc I'm getting this error:

>>> import pyodbc

>>> cnxn = pyodbc.connect('DRIVER={SQL Server};SERVER=adsf.com;DATABASE=asdf;UID=asdf;PWD=asdf')

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

pyodbc.Error: ('00000', '[00000] [iODBC][Driver Manager]dlopen({SQL Server}, 6): image not found (0) (SQLDriverConnect)')

edited Dec 2 '14 at 15:22

Will

7,67774865

asked Jul 26 '12 at 22:00

Ben Hamner

1,93521938

add a comment |

What's a good way to interface Python running on OS X with a cloud-based SQL Server database?

EDIT:

With pyodbc I'm getting this error:

>>> import pyodbc

>>> cnxn = pyodbc.connect('DRIVER={SQL Server};SERVER=adsf.com;DATABASE=asdf;UID=asdf;PWD=asdf')

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

pyodbc.Error: ('00000', '[00000] [iODBC][Driver Manager]dlopen({SQL Server}, 6): image not found (0) (SQLDriverConnect)')

edited Dec 2 '14 at 15:22

Will

7,67774865

asked Jul 26 '12 at 22:00

Ben Hamner

1,93521938

add a comment |

What's a good way to interface Python running on OS X with a cloud-based SQL Server database?

EDIT:

With pyodbc I'm getting this error:

>>> import pyodbc

>>> cnxn = pyodbc.connect('DRIVER={SQL Server};SERVER=adsf.com;DATABASE=asdf;UID=asdf;PWD=asdf')

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

pyodbc.Error: ('00000', '[00000] [iODBC][Driver Manager]dlopen({SQL Server}, 6): image not found (0) (SQLDriverConnect)')

edited Dec 2 '14 at 15:22

Will

7,67774865

asked Jul 26 '12 at 22:00

Ben Hamner

1,93521938

What's a good way to interface Python running on OS X with a cloud-based SQL Server database?

EDIT:

With pyodbc I'm getting this error:

>>> import pyodbc

>>> cnxn = pyodbc.connect('DRIVER={SQL Server};SERVER=adsf.com;DATABASE=asdf;UID=asdf;PWD=asdf')

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

pyodbc.Error: ('00000', '[00000] [iODBC][Driver Manager]dlopen({SQL Server}, 6): image not found (0) (SQLDriverConnect)')

python sql-server macos pyodbc

edited Dec 2 '14 at 15:22

Will

7,67774865

asked Jul 26 '12 at 22:00

Ben Hamner

1,93521938

edited Dec 2 '14 at 15:22

Will

7,67774865

asked Jul 26 '12 at 22:00

Ben Hamner

1,93521938

edited Dec 2 '14 at 15:22

Will

7,67774865

edited Dec 2 '14 at 15:22

Will

7,67774865

edited Dec 2 '14 at 15:22

Will

7,67774865

asked Jul 26 '12 at 22:00

Ben Hamner

1,93521938

asked Jul 26 '12 at 22:00

Ben Hamner

1,93521938

asked Jul 26 '12 at 22:00

Ben Hamner

1,93521938

add a comment |

7 Answers
7

active

oldest

votes

SQLAlchemy is probably your best bet. It has an ORM, but doesn't require its use. MS SQL is supported through a number of DBAPI projects.

As for lower-level interfaces, here's the three DBAPI projects listed at SQLAlchemy's site that have vanilla Python and Unix support:

pymssql appears to be the simplest to set up; it doesn't require FreeTDS.

pyodbc appears to be under more active development than pymssql.

mxODBC is a commercially-licensed interface to many databases.

edited Jul 26 '12 at 22:21

answered Jul 26 '12 at 22:16

Colin Dunklau

2,3461318

6

Is there any chance someone can actually answer the original question? I have the same problem and I'm having a hard time finding a solution. This answer from Colin suggests using pyodbc, but from the OP's error, we can see he is using pyodbc already. Furthermore, he's on OSX, so Unix solutions will not necessarily apply...

– Dannid
Feb 25 '13 at 23:48

1

@Dannid: The original question was "What's a good way to interface Python running on OS X with a cloud-based SQL Server database?", which was what I answered. Try asking your own question with details on what's wrong.

– Colin Dunklau
Feb 28 '13 at 2:29

@Dannid: Ben Hamner apparently asked another question about the error he had with pyodbc, but alas, he apparently had to hit it with the "reinstall SQL Server" hammer. Good luck!

– Colin Dunklau
Feb 28 '13 at 2:33

add a comment |

Summary

I'm using a Mac on Yosemite Version 10.10.1 trying to connect to a MS SQL Server database. I searched and couldn't find an updated detailed answer so here's a writeup that is mostly from this amazing article here. I'm adding it on stackoverflow in case the link dies. The idea is that we'll have the following layers to setup/connect.

Layers

PART 1 - pyodbc

PART 2 - freeTDS (can check with tsql)

PART 3 - unixODBC (can check with isql)

PART 4 - MS SQL (can check with a regular python program)

Steps

Install Homebrew from here - this is a package manager for Mac OSX. The article shows how to use another package manager 'MacPorts'. For my instructions, they're with homebrew. Basically homebrew has a folder 'cellar' that holds different versions of packages. Instead of modifying your normal files, it instead points to these homebrew packages.

We need to install Pyodbc, but pyodbc uses iODBC drivers by default (which comes installed with mac), but many people have issues making it work. So, we're going to use an alternative called unixodbc, which we would install in the future. For now, we need to configure the pyodbc installation such that it works with unixodbc.

Go to PyPi and download pyodbc tarball and uncompress it. Then change these lines in setup.py:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('iodbc')

to:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('odbc')

and now run python setup.py install.

This makes our pyodbc installation use unixodbc drivers by default. Perfect!

Install FreeTDS with brew install freetds --with-unixodbc (FreeTDS is the driver that sits between the Mac ODBC and MS SQL Server, this chart here shows which version of TDS you should be using based on your specific Microsoft Server version; e.g. tds protocol 7.2 for Microsoft SQL Server 2008).

Configure freetds.conf file (The file should be in '/usr/local/etc/freetds.conf', which for Homebrew is a link to say '/usr/local/Cellar/freetds/0.91_2/etc', but yours might be somewhere different depending on version). I edited the global and added my database info to the end (for some reason 'tds version = 7.2' would throw an error, but still work, while 8.0 just works):
```
[global]

# TDS protocol version

tds version = 8.0



[MYSERVER]

host = MYSERVER

port = 1433

tds version = 8.0
```

Verify FreeTDS installed correctly with: tsql -S myserver -U myuser -P mypassword (you should see a prompt like this if it worked)
```
locale is "en_US.UTF-8"

locale charset is "UTF-8"

using default charset "UTF-8"

1>
```

Install unixODBC with brew install unixodbc.

Setup your unixODBC config files, which includes odbcinst.ini (driver configuration), and odbc.ini (DSN configuration file). By default, my files were in: /Library/ODBC (Note: NOT my user library aka /Users/williamliu/Library). Or they could also be in your homebrew installation directory /usr/local/Cellar/unixodbc/<version>/etc.

Open up your 'odbcinst.ini' file and then add the following (Note: Different if you use MacPorts. For Homebrew, this file is a link to the homebrew version e.g. mine is in '/usr/local/Cellar/freetds/0.91_2/lib/libtdsodbc.so'):
```
[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1
```

Open up your 'odbc.ini' and then add the following (this is usually along with odbcinst.ini:

[MYSERVER]

Description         = Test to SQLServer

Driver              = FreeTDS

Trace               = Yes

TraceFile           = /tmp/sql.log

Database            = MYDATABASE

Servername          = MYSERVER

UserName            = MYUSER

Password            = MYPASSWORD

Port                = 1433

Protocol            = 8.0

ReadOnly            = No

RowVersioning       = No

ShowSystemTables    = No

ShowOidColumn       = No

FakeOidIndex        = No

Verify unixODBC installed correctly with: isql MYSERVER MYUSER MYPASSWORD. If you get an error that you cannot connect, then add -v to check what the verbose output is and fix it. Otherwise, you should see this:

+---------------------------------------+

| Connected!                            |

|                                       |

| sql-statement                         |

| help [tablename]                      |

| quit                                  |

|                                       |

+---------------------------------------+

Now verify pyodbc works with a python program. Run python in the shell or a .py file with this and you should get your query back:

import pyodbc

import pandas

import pandas.io.sql as psql



cnxn = pyodbc.connect('DSN=MYSERVER;UID=MYUSER;PWD=MYPASSWORD')

cursor = cnxn.cursor()

sql = ("SELECT * FROM dbo.MYDATABASE")

df = psql.frame_query(sql, cnxn)

You can refer to the documentation of pyodbc to get more help after this.

edited Dec 29 '14 at 19:32

Forbidden Overseer

1,78342140

answered Dec 1 '14 at 23:54

Will

7,67774865

3

Nice answer! I just did a LOT of searching and finally got this working. I think you should change the order of those 11 steps. (Installing TDSServer before unixodbc) because we have to specify the driver in odbc ini file. Also, while installing pyodbc, I had to change the setting in setup.py for drivers from iodbc to odbc to make it use unixodbc, and then install it. You should update 2nd step with this step, and then I guess answer would be complete. :)

– Forbidden Overseer
Dec 26 '14 at 11:44

1

I currently don't have access to a Mac so I can't test it, but feel free to make the edit and I'll accept.

– Will
Dec 29 '14 at 17:48

2

I've installed freetds via brew install freetds --with-unixodbc, and pymssql via pip install pymssql. Then pymssql works well in python

– cdarlint
Jun 10 '15 at 5:25

2

New tarballs don't include iodbc anymore, so you should be able to skip that step now.

– nerdwaller
May 2 '16 at 13:35

add a comment |

I've been able to simplify this and repeatedly have it work in my environments as of May 2016:

Install FreeTDS

brew install freetds --with-unixodbc

Install PYODBC

Extrapolated from Reference

pip install -U 

    --global-option=build_ext 

    --global-option="-I/usr/local/include" 

    --global-option="-L/usr/local/lib" 

    pyodbc

Tell UnixODBC about the FreeTDS Driver

Note: You may have a different version

cat <<'EOF' >> /usr/local/Cellar/unixodbc/2.3.4/etc/odbcinst.ini

[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1

EOF

From there, I had to tell pyodbc to use the FreeTDS Driver:

dsn = 'DRIVER=FreeTDS;DATABASE=MyDb;SERVER=...'

This is fantastic as now you can use it with aioodbc if you are doing async programming in Python 3.x:

async with aioodbc.connect(dsn=dsn, loop=asyncio.get_event_loop()) as conn:

    async with conn.cursor() as cur:

        await cur.execute('SELECT 42')

        r = await cur.fetchall()

        print(r)

Alternatively: You can use pymssql flat out, but that won't work if you want to use odbc or asyncio.

edited May 23 '17 at 10:31

Community♦

answered May 2 '16 at 15:06

nerdwaller

1,2781318

add a comment |

Will's answer was really helpful to me.

Here are some notes on a couple differences I experienced along the way, in case they help others:

The pyodbc tarball already had the change required, so all I had to do was download it and run python setup.py install. (Note: The version I had installed with pip was still using iodbc, so that didn't work.

The Verify FreeTDS installed step didn't allow me to connect to the database because I don't have access to the master, and there is apparently no way to specify. This seems to be a well known issue. I wasted a bunch of time trying to solve it, but failed and in the end it didn't block other steps from working.

These instructions say to put the username and password in odbc.ini. Since we need to say the login credentials again when we log in, I tried removing the UserName and Password from odbc.ini, hoping they weren't really necessary. (I'd rather have my password written down in fewer places!) This worked fine.

I had to add the host to the userid in isql MYSERVER myname@foo.bar.com MYPASSWORD (and in the Python code).

(I hoped that this would mean I don't need the host in freetds.conf, but alas, that has to stay.)

edited Aug 15 '17 at 19:34

JakeGould

20.7k84975

answered May 21 '15 at 14:18

DavidC

764515

add a comment |

I am on macOS Sierra 10.12.3. pymssql did the job perfectly. If nothing works from other upvoted answers, follow this:

brew unlink freetds

brew install homebrew/versions/freetds091

pip install pymssql

and here is a sample snippet to establish connection:

conn = pymssql.connect(serverhostname, username, password, dbname)

cursor = conn.cursor()

cursor.execute('SELECT * FROM users')

answered Feb 6 '17 at 5:09

intrepidkarthi

2,21083473

add a comment |

Pyodbc + MS's own odbc provider, msodbcsql, rather than FreeTDS. My reasoning was simple - who is most motivated to have good SQL Server support? MS.

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-connect-query-python

It really was pretty simple, the main hassle is that their installer only works with Homebrew, rather than macports which is what I usually use. I first tried to install Homebrew to my home directory, but the actual drivers aren't "seen" by pyodbc that way, so did a standard Homebrew install, then brew install msodbcsql. This resulted in the following packages:

(venv) jluc@sandbox$ brew list

 msodbcsql  openssl     unixodbc

Connect string that worked for me:

Driver={ODBC Driver 13 for SQL Server};Server=192.168.1.xxx;Database=mydb;Uid=myuser;Pwd=mypassword;

And, for SQL Alchemy:

"mssql+pyodbc://%(user)s:%(password)s@%(hostname)s:%(port)s/%(dbname)s?driver=ODBC+Driver+13+for+SQL+Server"

If you're also installing MS SQL Server (I got the 2016 Developer Edition), remember to : 1) use SQL Server Configuration Manager (SQLServerManager13.msc) to enable TCPIP on port 1433, for your IP. 2) open up port 1433 in Windows Firewall (wf.msc). MS config instructions

Versions: Sierra, Python 2.7, SQL Server 2016 Dev edition, Win 10 Pro.

Note: be careful around MS’s brew install. I think it used to take the initiative to install Homebrew. Not sure if it would’ve been an issue in practice.

edited Nov 22 '18 at 6:55

answered Jun 27 '17 at 20:53

JL Peyret

3,0951630

Going to route of installing the Microsoft ODBC drivers fixed the issue for me. Good suggestions here: superuser.com/questions/1355732/…

– Snympi
Nov 21 '18 at 14:19

add a comment |

There are a lot of hoops to jump through. Will's answer outlines a good number of them.

After much struggle, I managed to get this working with Docker (so this should work anywhere that runs docker).

I have tested the setup with Python 3.6 and Python 2.7: with pyodbc==3.0.10, django-pyodbc-azure and Django 1.10.4 (this setup is for Django, but works for vanilla python as well).

I've created a public image which you can use: https://hub.docker.com/r/toast38coza/python-mssql/

Here is a simple working docker setup:

version: "3"

services:

  db:

    restart: on-failure:10

    image: microsoft/mssql-server-linux:latest

    environment:

      - ACCEPT_EULA=Y

      - SA_PASSWORD=SuperSecret(!)100

    ports:

      - "1433:1433"

  py:

    image: toast38coza/python-mssql

    links:

      - db

    environment:

      - SA_PASSWORD=SuperSecret(!)100

      - DB_NAME=mydb

Now you can run:

docker-compose run --rm py python

Which will run the python cli inside the py service above

Then try create a database:

>>> import pyodbc, os

>>> db_name = os.environ.get('DB_NAME')

>>> pwd = os.environ.get('SA_PASSWORD')

>>> connection_string = "driver=FreeTDS;server=db;PORT=1433 database=master;UID=sa;PWD={};TDS_Version=8.0;".format(pwd)

>>> conn = pyodbc.connect(connection_string, autocommit=True)

>>> conn.execute('create database {}'.format(db_name))

<pyodbc.Cursor object at 0x7fb3067f0e70>

That should create a database called mydb (the DB_NAME from the docker-compose file environment variable). Note: because we've created the link to the db service (running MS SQL), we can use the hostname db. If you are connecting to an external MS SQL setup, you obviously don't need the db service (and edit your connection string accordingly)

If you're using Django, there is a more complete example in the repo, but, just a heads up, you will need your settings to look something like this:

DATABASES = {

    'default': {

        'ENGINE': "sql_server.pyodbc",

        'HOST': "db",

        'PORT':'1433',

        'USER': "sa",

        'PASSWORD': os.environ.get('SA_PASSWORD'),

        'NAME': os.environ.get('DB_NAME'),

        'OPTIONS': {

            "driver": "FreeTDS",

            "host_is_server": True,

            "unicode_results": True,

            "extra_params": "tds_version=8.0",

        }

    }

}

answered Apr 11 '17 at 10:28

toast38coza

4,87313025

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f11678696%2fsql-server-python-and-os-x%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

7 Answers
7

active

oldest

votes

7 Answers
7

active

oldest

votes

SQLAlchemy is probably your best bet. It has an ORM, but doesn't require its use. MS SQL is supported through a number of DBAPI projects.

As for lower-level interfaces, here's the three DBAPI projects listed at SQLAlchemy's site that have vanilla Python and Unix support:

pymssql appears to be the simplest to set up; it doesn't require FreeTDS.

pyodbc appears to be under more active development than pymssql.

mxODBC is a commercially-licensed interface to many databases.

edited Jul 26 '12 at 22:21

answered Jul 26 '12 at 22:16

Colin Dunklau

2,3461318

6

Is there any chance someone can actually answer the original question? I have the same problem and I'm having a hard time finding a solution. This answer from Colin suggests using pyodbc, but from the OP's error, we can see he is using pyodbc already. Furthermore, he's on OSX, so Unix solutions will not necessarily apply...

– Dannid
Feb 25 '13 at 23:48

1

@Dannid: The original question was "What's a good way to interface Python running on OS X with a cloud-based SQL Server database?", which was what I answered. Try asking your own question with details on what's wrong.

– Colin Dunklau
Feb 28 '13 at 2:29

@Dannid: Ben Hamner apparently asked another question about the error he had with pyodbc, but alas, he apparently had to hit it with the "reinstall SQL Server" hammer. Good luck!

– Colin Dunklau
Feb 28 '13 at 2:33

add a comment |

SQLAlchemy is probably your best bet. It has an ORM, but doesn't require its use. MS SQL is supported through a number of DBAPI projects.

As for lower-level interfaces, here's the three DBAPI projects listed at SQLAlchemy's site that have vanilla Python and Unix support:

pymssql appears to be the simplest to set up; it doesn't require FreeTDS.

pyodbc appears to be under more active development than pymssql.

mxODBC is a commercially-licensed interface to many databases.

edited Jul 26 '12 at 22:21

answered Jul 26 '12 at 22:16

Colin Dunklau

2,3461318

6

Is there any chance someone can actually answer the original question? I have the same problem and I'm having a hard time finding a solution. This answer from Colin suggests using pyodbc, but from the OP's error, we can see he is using pyodbc already. Furthermore, he's on OSX, so Unix solutions will not necessarily apply...

– Dannid
Feb 25 '13 at 23:48

1

@Dannid: The original question was "What's a good way to interface Python running on OS X with a cloud-based SQL Server database?", which was what I answered. Try asking your own question with details on what's wrong.

– Colin Dunklau
Feb 28 '13 at 2:29

@Dannid: Ben Hamner apparently asked another question about the error he had with pyodbc, but alas, he apparently had to hit it with the "reinstall SQL Server" hammer. Good luck!

– Colin Dunklau
Feb 28 '13 at 2:33

add a comment |

SQLAlchemy is probably your best bet. It has an ORM, but doesn't require its use. MS SQL is supported through a number of DBAPI projects.

As for lower-level interfaces, here's the three DBAPI projects listed at SQLAlchemy's site that have vanilla Python and Unix support:

pymssql appears to be the simplest to set up; it doesn't require FreeTDS.

pyodbc appears to be under more active development than pymssql.

mxODBC is a commercially-licensed interface to many databases.

edited Jul 26 '12 at 22:21

answered Jul 26 '12 at 22:16

Colin Dunklau

2,3461318

SQLAlchemy is probably your best bet. It has an ORM, but doesn't require its use. MS SQL is supported through a number of DBAPI projects.

As for lower-level interfaces, here's the three DBAPI projects listed at SQLAlchemy's site that have vanilla Python and Unix support:

pymssql appears to be the simplest to set up; it doesn't require FreeTDS.

pyodbc appears to be under more active development than pymssql.

mxODBC is a commercially-licensed interface to many databases.

edited Jul 26 '12 at 22:21

answered Jul 26 '12 at 22:16

Colin Dunklau

2,3461318

edited Jul 26 '12 at 22:21

answered Jul 26 '12 at 22:16

Colin Dunklau

2,3461318

answered Jul 26 '12 at 22:16

Colin Dunklau

2,3461318

answered Jul 26 '12 at 22:16

Colin Dunklau

2,3461318

6

Is there any chance someone can actually answer the original question? I have the same problem and I'm having a hard time finding a solution. This answer from Colin suggests using pyodbc, but from the OP's error, we can see he is using pyodbc already. Furthermore, he's on OSX, so Unix solutions will not necessarily apply...

– Dannid
Feb 25 '13 at 23:48

1

@Dannid: The original question was "What's a good way to interface Python running on OS X with a cloud-based SQL Server database?", which was what I answered. Try asking your own question with details on what's wrong.

– Colin Dunklau
Feb 28 '13 at 2:29

@Dannid: Ben Hamner apparently asked another question about the error he had with pyodbc, but alas, he apparently had to hit it with the "reinstall SQL Server" hammer. Good luck!

– Colin Dunklau
Feb 28 '13 at 2:33

add a comment |

6

Is there any chance someone can actually answer the original question? I have the same problem and I'm having a hard time finding a solution. This answer from Colin suggests using pyodbc, but from the OP's error, we can see he is using pyodbc already. Furthermore, he's on OSX, so Unix solutions will not necessarily apply...

– Dannid
Feb 25 '13 at 23:48

1

@Dannid: The original question was "What's a good way to interface Python running on OS X with a cloud-based SQL Server database?", which was what I answered. Try asking your own question with details on what's wrong.

– Colin Dunklau
Feb 28 '13 at 2:29

@Dannid: Ben Hamner apparently asked another question about the error he had with pyodbc, but alas, he apparently had to hit it with the "reinstall SQL Server" hammer. Good luck!

– Colin Dunklau
Feb 28 '13 at 2:33

Is there any chance someone can actually answer the original question? I have the same problem and I'm having a hard time finding a solution. This answer from Colin suggests using pyodbc, but from the OP's error, we can see he is using pyodbc already. Furthermore, he's on OSX, so Unix solutions will not necessarily apply...

– Dannid
Feb 25 '13 at 23:48

@Dannid: The original question was "What's a good way to interface Python running on OS X with a cloud-based SQL Server database?", which was what I answered. Try asking your own question with details on what's wrong.

– Colin Dunklau
Feb 28 '13 at 2:29

@Dannid: Ben Hamner apparently asked another question about the error he had with pyodbc, but alas, he apparently had to hit it with the "reinstall SQL Server" hammer. Good luck!

– Colin Dunklau
Feb 28 '13 at 2:33

add a comment |

Summary

Layers

PART 1 - pyodbc

PART 2 - freeTDS (can check with tsql)

PART 3 - unixODBC (can check with isql)

PART 4 - MS SQL (can check with a regular python program)

Steps

Install Homebrew from here - this is a package manager for Mac OSX. The article shows how to use another package manager 'MacPorts'. For my instructions, they're with homebrew. Basically homebrew has a folder 'cellar' that holds different versions of packages. Instead of modifying your normal files, it instead points to these homebrew packages.

We need to install Pyodbc, but pyodbc uses iODBC drivers by default (which comes installed with mac), but many people have issues making it work. So, we're going to use an alternative called unixodbc, which we would install in the future. For now, we need to configure the pyodbc installation such that it works with unixodbc.

Go to PyPi and download pyodbc tarball and uncompress it. Then change these lines in setup.py:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('iodbc')

to:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('odbc')

and now run python setup.py install.

This makes our pyodbc installation use unixodbc drivers by default. Perfect!

Install FreeTDS with brew install freetds --with-unixodbc (FreeTDS is the driver that sits between the Mac ODBC and MS SQL Server, this chart here shows which version of TDS you should be using based on your specific Microsoft Server version; e.g. tds protocol 7.2 for Microsoft SQL Server 2008).

Configure freetds.conf file (The file should be in '/usr/local/etc/freetds.conf', which for Homebrew is a link to say '/usr/local/Cellar/freetds/0.91_2/etc', but yours might be somewhere different depending on version). I edited the global and added my database info to the end (for some reason 'tds version = 7.2' would throw an error, but still work, while 8.0 just works):
```
[global]

# TDS protocol version

tds version = 8.0



[MYSERVER]

host = MYSERVER

port = 1433

tds version = 8.0
```

Verify FreeTDS installed correctly with: tsql -S myserver -U myuser -P mypassword (you should see a prompt like this if it worked)
```
locale is "en_US.UTF-8"

locale charset is "UTF-8"

using default charset "UTF-8"

1>
```

Install unixODBC with brew install unixodbc.

Setup your unixODBC config files, which includes odbcinst.ini (driver configuration), and odbc.ini (DSN configuration file). By default, my files were in: /Library/ODBC (Note: NOT my user library aka /Users/williamliu/Library). Or they could also be in your homebrew installation directory /usr/local/Cellar/unixodbc/<version>/etc.

Open up your 'odbcinst.ini' file and then add the following (Note: Different if you use MacPorts. For Homebrew, this file is a link to the homebrew version e.g. mine is in '/usr/local/Cellar/freetds/0.91_2/lib/libtdsodbc.so'):
```
[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1
```

Open up your 'odbc.ini' and then add the following (this is usually along with odbcinst.ini:

[MYSERVER]

Description         = Test to SQLServer

Driver              = FreeTDS

Trace               = Yes

TraceFile           = /tmp/sql.log

Database            = MYDATABASE

Servername          = MYSERVER

UserName            = MYUSER

Password            = MYPASSWORD

Port                = 1433

Protocol            = 8.0

ReadOnly            = No

RowVersioning       = No

ShowSystemTables    = No

ShowOidColumn       = No

FakeOidIndex        = No

+---------------------------------------+

| Connected!                            |

|                                       |

| sql-statement                         |

| help [tablename]                      |

| quit                                  |

|                                       |

+---------------------------------------+

Now verify pyodbc works with a python program. Run python in the shell or a .py file with this and you should get your query back:

import pyodbc

import pandas

import pandas.io.sql as psql



cnxn = pyodbc.connect('DSN=MYSERVER;UID=MYUSER;PWD=MYPASSWORD')

cursor = cnxn.cursor()

sql = ("SELECT * FROM dbo.MYDATABASE")

df = psql.frame_query(sql, cnxn)

You can refer to the documentation of pyodbc to get more help after this.

edited Dec 29 '14 at 19:32

Forbidden Overseer

1,78342140

answered Dec 1 '14 at 23:54

Will

7,67774865

3

Nice answer! I just did a LOT of searching and finally got this working. I think you should change the order of those 11 steps. (Installing TDSServer before unixodbc) because we have to specify the driver in odbc ini file. Also, while installing pyodbc, I had to change the setting in setup.py for drivers from iodbc to odbc to make it use unixodbc, and then install it. You should update 2nd step with this step, and then I guess answer would be complete. :)

– Forbidden Overseer
Dec 26 '14 at 11:44

1

I currently don't have access to a Mac so I can't test it, but feel free to make the edit and I'll accept.

– Will
Dec 29 '14 at 17:48

2

I've installed freetds via brew install freetds --with-unixodbc, and pymssql via pip install pymssql. Then pymssql works well in python

– cdarlint
Jun 10 '15 at 5:25

2

New tarballs don't include iodbc anymore, so you should be able to skip that step now.

– nerdwaller
May 2 '16 at 13:35

add a comment |

Summary

Layers

PART 1 - pyodbc

PART 2 - freeTDS (can check with tsql)

PART 3 - unixODBC (can check with isql)

PART 4 - MS SQL (can check with a regular python program)

Steps

Install Homebrew from here - this is a package manager for Mac OSX. The article shows how to use another package manager 'MacPorts'. For my instructions, they're with homebrew. Basically homebrew has a folder 'cellar' that holds different versions of packages. Instead of modifying your normal files, it instead points to these homebrew packages.

We need to install Pyodbc, but pyodbc uses iODBC drivers by default (which comes installed with mac), but many people have issues making it work. So, we're going to use an alternative called unixodbc, which we would install in the future. For now, we need to configure the pyodbc installation such that it works with unixodbc.

Go to PyPi and download pyodbc tarball and uncompress it. Then change these lines in setup.py:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('iodbc')

to:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('odbc')

and now run python setup.py install.

This makes our pyodbc installation use unixodbc drivers by default. Perfect!

Install FreeTDS with brew install freetds --with-unixodbc (FreeTDS is the driver that sits between the Mac ODBC and MS SQL Server, this chart here shows which version of TDS you should be using based on your specific Microsoft Server version; e.g. tds protocol 7.2 for Microsoft SQL Server 2008).

Configure freetds.conf file (The file should be in '/usr/local/etc/freetds.conf', which for Homebrew is a link to say '/usr/local/Cellar/freetds/0.91_2/etc', but yours might be somewhere different depending on version). I edited the global and added my database info to the end (for some reason 'tds version = 7.2' would throw an error, but still work, while 8.0 just works):
```
[global]

# TDS protocol version

tds version = 8.0



[MYSERVER]

host = MYSERVER

port = 1433

tds version = 8.0
```

Verify FreeTDS installed correctly with: tsql -S myserver -U myuser -P mypassword (you should see a prompt like this if it worked)
```
locale is "en_US.UTF-8"

locale charset is "UTF-8"

using default charset "UTF-8"

1>
```

Install unixODBC with brew install unixodbc.

Setup your unixODBC config files, which includes odbcinst.ini (driver configuration), and odbc.ini (DSN configuration file). By default, my files were in: /Library/ODBC (Note: NOT my user library aka /Users/williamliu/Library). Or they could also be in your homebrew installation directory /usr/local/Cellar/unixodbc/<version>/etc.

Open up your 'odbcinst.ini' file and then add the following (Note: Different if you use MacPorts. For Homebrew, this file is a link to the homebrew version e.g. mine is in '/usr/local/Cellar/freetds/0.91_2/lib/libtdsodbc.so'):
```
[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1
```

Open up your 'odbc.ini' and then add the following (this is usually along with odbcinst.ini:

[MYSERVER]

Description         = Test to SQLServer

Driver              = FreeTDS

Trace               = Yes

TraceFile           = /tmp/sql.log

Database            = MYDATABASE

Servername          = MYSERVER

UserName            = MYUSER

Password            = MYPASSWORD

Port                = 1433

Protocol            = 8.0

ReadOnly            = No

RowVersioning       = No

ShowSystemTables    = No

ShowOidColumn       = No

FakeOidIndex        = No

+---------------------------------------+

| Connected!                            |

|                                       |

| sql-statement                         |

| help [tablename]                      |

| quit                                  |

|                                       |

+---------------------------------------+

Now verify pyodbc works with a python program. Run python in the shell or a .py file with this and you should get your query back:

import pyodbc

import pandas

import pandas.io.sql as psql



cnxn = pyodbc.connect('DSN=MYSERVER;UID=MYUSER;PWD=MYPASSWORD')

cursor = cnxn.cursor()

sql = ("SELECT * FROM dbo.MYDATABASE")

df = psql.frame_query(sql, cnxn)

You can refer to the documentation of pyodbc to get more help after this.

edited Dec 29 '14 at 19:32

Forbidden Overseer

1,78342140

answered Dec 1 '14 at 23:54

Will

7,67774865

3

Nice answer! I just did a LOT of searching and finally got this working. I think you should change the order of those 11 steps. (Installing TDSServer before unixodbc) because we have to specify the driver in odbc ini file. Also, while installing pyodbc, I had to change the setting in setup.py for drivers from iodbc to odbc to make it use unixodbc, and then install it. You should update 2nd step with this step, and then I guess answer would be complete. :)

– Forbidden Overseer
Dec 26 '14 at 11:44

1

I currently don't have access to a Mac so I can't test it, but feel free to make the edit and I'll accept.

– Will
Dec 29 '14 at 17:48

2

I've installed freetds via brew install freetds --with-unixodbc, and pymssql via pip install pymssql. Then pymssql works well in python

– cdarlint
Jun 10 '15 at 5:25

2

New tarballs don't include iodbc anymore, so you should be able to skip that step now.

– nerdwaller
May 2 '16 at 13:35

add a comment |

Summary

Layers

PART 1 - pyodbc

PART 2 - freeTDS (can check with tsql)

PART 3 - unixODBC (can check with isql)

PART 4 - MS SQL (can check with a regular python program)

Steps

Install Homebrew from here - this is a package manager for Mac OSX. The article shows how to use another package manager 'MacPorts'. For my instructions, they're with homebrew. Basically homebrew has a folder 'cellar' that holds different versions of packages. Instead of modifying your normal files, it instead points to these homebrew packages.

We need to install Pyodbc, but pyodbc uses iODBC drivers by default (which comes installed with mac), but many people have issues making it work. So, we're going to use an alternative called unixodbc, which we would install in the future. For now, we need to configure the pyodbc installation such that it works with unixodbc.

Go to PyPi and download pyodbc tarball and uncompress it. Then change these lines in setup.py:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('iodbc')

to:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('odbc')

and now run python setup.py install.

This makes our pyodbc installation use unixodbc drivers by default. Perfect!

Install FreeTDS with brew install freetds --with-unixodbc (FreeTDS is the driver that sits between the Mac ODBC and MS SQL Server, this chart here shows which version of TDS you should be using based on your specific Microsoft Server version; e.g. tds protocol 7.2 for Microsoft SQL Server 2008).

Configure freetds.conf file (The file should be in '/usr/local/etc/freetds.conf', which for Homebrew is a link to say '/usr/local/Cellar/freetds/0.91_2/etc', but yours might be somewhere different depending on version). I edited the global and added my database info to the end (for some reason 'tds version = 7.2' would throw an error, but still work, while 8.0 just works):
```
[global]

# TDS protocol version

tds version = 8.0



[MYSERVER]

host = MYSERVER

port = 1433

tds version = 8.0
```

Verify FreeTDS installed correctly with: tsql -S myserver -U myuser -P mypassword (you should see a prompt like this if it worked)
```
locale is "en_US.UTF-8"

locale charset is "UTF-8"

using default charset "UTF-8"

1>
```

Install unixODBC with brew install unixodbc.

Setup your unixODBC config files, which includes odbcinst.ini (driver configuration), and odbc.ini (DSN configuration file). By default, my files were in: /Library/ODBC (Note: NOT my user library aka /Users/williamliu/Library). Or they could also be in your homebrew installation directory /usr/local/Cellar/unixodbc/<version>/etc.

Open up your 'odbcinst.ini' file and then add the following (Note: Different if you use MacPorts. For Homebrew, this file is a link to the homebrew version e.g. mine is in '/usr/local/Cellar/freetds/0.91_2/lib/libtdsodbc.so'):
```
[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1
```

Open up your 'odbc.ini' and then add the following (this is usually along with odbcinst.ini:

[MYSERVER]

Description         = Test to SQLServer

Driver              = FreeTDS

Trace               = Yes

TraceFile           = /tmp/sql.log

Database            = MYDATABASE

Servername          = MYSERVER

UserName            = MYUSER

Password            = MYPASSWORD

Port                = 1433

Protocol            = 8.0

ReadOnly            = No

RowVersioning       = No

ShowSystemTables    = No

ShowOidColumn       = No

FakeOidIndex        = No

+---------------------------------------+

| Connected!                            |

|                                       |

| sql-statement                         |

| help [tablename]                      |

| quit                                  |

|                                       |

+---------------------------------------+

Now verify pyodbc works with a python program. Run python in the shell or a .py file with this and you should get your query back:

import pyodbc

import pandas

import pandas.io.sql as psql



cnxn = pyodbc.connect('DSN=MYSERVER;UID=MYUSER;PWD=MYPASSWORD')

cursor = cnxn.cursor()

sql = ("SELECT * FROM dbo.MYDATABASE")

df = psql.frame_query(sql, cnxn)

You can refer to the documentation of pyodbc to get more help after this.

edited Dec 29 '14 at 19:32

Forbidden Overseer

1,78342140

answered Dec 1 '14 at 23:54

Will

7,67774865

Summary

Layers

PART 1 - pyodbc

PART 2 - freeTDS (can check with tsql)

PART 3 - unixODBC (can check with isql)

PART 4 - MS SQL (can check with a regular python program)

Steps

Install Homebrew from here - this is a package manager for Mac OSX. The article shows how to use another package manager 'MacPorts'. For my instructions, they're with homebrew. Basically homebrew has a folder 'cellar' that holds different versions of packages. Instead of modifying your normal files, it instead points to these homebrew packages.

We need to install Pyodbc, but pyodbc uses iODBC drivers by default (which comes installed with mac), but many people have issues making it work. So, we're going to use an alternative called unixodbc, which we would install in the future. For now, we need to configure the pyodbc installation such that it works with unixodbc.

Go to PyPi and download pyodbc tarball and uncompress it. Then change these lines in setup.py:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('iodbc')

to:

elif sys.platform == 'darwin':

        # OS/X now ships with iODBC.

        settings['libraries'].append('odbc')

and now run python setup.py install.

This makes our pyodbc installation use unixodbc drivers by default. Perfect!

Install FreeTDS with brew install freetds --with-unixodbc (FreeTDS is the driver that sits between the Mac ODBC and MS SQL Server, this chart here shows which version of TDS you should be using based on your specific Microsoft Server version; e.g. tds protocol 7.2 for Microsoft SQL Server 2008).

Configure freetds.conf file (The file should be in '/usr/local/etc/freetds.conf', which for Homebrew is a link to say '/usr/local/Cellar/freetds/0.91_2/etc', but yours might be somewhere different depending on version). I edited the global and added my database info to the end (for some reason 'tds version = 7.2' would throw an error, but still work, while 8.0 just works):
```
[global]

# TDS protocol version

tds version = 8.0



[MYSERVER]

host = MYSERVER

port = 1433

tds version = 8.0
```

Verify FreeTDS installed correctly with: tsql -S myserver -U myuser -P mypassword (you should see a prompt like this if it worked)
```
locale is "en_US.UTF-8"

locale charset is "UTF-8"

using default charset "UTF-8"

1>
```

Install unixODBC with brew install unixodbc.

Setup your unixODBC config files, which includes odbcinst.ini (driver configuration), and odbc.ini (DSN configuration file). By default, my files were in: /Library/ODBC (Note: NOT my user library aka /Users/williamliu/Library). Or they could also be in your homebrew installation directory /usr/local/Cellar/unixodbc/<version>/etc.

Open up your 'odbcinst.ini' file and then add the following (Note: Different if you use MacPorts. For Homebrew, this file is a link to the homebrew version e.g. mine is in '/usr/local/Cellar/freetds/0.91_2/lib/libtdsodbc.so'):
```
[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1
```

Open up your 'odbc.ini' and then add the following (this is usually along with odbcinst.ini:

[MYSERVER]

Description         = Test to SQLServer

Driver              = FreeTDS

Trace               = Yes

TraceFile           = /tmp/sql.log

Database            = MYDATABASE

Servername          = MYSERVER

UserName            = MYUSER

Password            = MYPASSWORD

Port                = 1433

Protocol            = 8.0

ReadOnly            = No

RowVersioning       = No

ShowSystemTables    = No

ShowOidColumn       = No

FakeOidIndex        = No

+---------------------------------------+

| Connected!                            |

|                                       |

| sql-statement                         |

| help [tablename]                      |

| quit                                  |

|                                       |

+---------------------------------------+

Now verify pyodbc works with a python program. Run python in the shell or a .py file with this and you should get your query back:

import pyodbc

import pandas

import pandas.io.sql as psql



cnxn = pyodbc.connect('DSN=MYSERVER;UID=MYUSER;PWD=MYPASSWORD')

cursor = cnxn.cursor()

sql = ("SELECT * FROM dbo.MYDATABASE")

df = psql.frame_query(sql, cnxn)

You can refer to the documentation of pyodbc to get more help after this.

edited Dec 29 '14 at 19:32

Forbidden Overseer

1,78342140

answered Dec 1 '14 at 23:54

Will

7,67774865

edited Dec 29 '14 at 19:32

Forbidden Overseer

1,78342140

edited Dec 29 '14 at 19:32

Forbidden Overseer

1,78342140

edited Dec 29 '14 at 19:32

Forbidden Overseer

1,78342140

answered Dec 1 '14 at 23:54

Will

7,67774865

answered Dec 1 '14 at 23:54

Will

7,67774865

answered Dec 1 '14 at 23:54

Will

7,67774865

3

Nice answer! I just did a LOT of searching and finally got this working. I think you should change the order of those 11 steps. (Installing TDSServer before unixodbc) because we have to specify the driver in odbc ini file. Also, while installing pyodbc, I had to change the setting in setup.py for drivers from iodbc to odbc to make it use unixodbc, and then install it. You should update 2nd step with this step, and then I guess answer would be complete. :)

– Forbidden Overseer
Dec 26 '14 at 11:44

1

I currently don't have access to a Mac so I can't test it, but feel free to make the edit and I'll accept.

– Will
Dec 29 '14 at 17:48

2

I've installed freetds via brew install freetds --with-unixodbc, and pymssql via pip install pymssql. Then pymssql works well in python

– cdarlint
Jun 10 '15 at 5:25

2

New tarballs don't include iodbc anymore, so you should be able to skip that step now.

– nerdwaller
May 2 '16 at 13:35

add a comment |

3

Nice answer! I just did a LOT of searching and finally got this working. I think you should change the order of those 11 steps. (Installing TDSServer before unixodbc) because we have to specify the driver in odbc ini file. Also, while installing pyodbc, I had to change the setting in setup.py for drivers from iodbc to odbc to make it use unixodbc, and then install it. You should update 2nd step with this step, and then I guess answer would be complete. :)

– Forbidden Overseer
Dec 26 '14 at 11:44

1

I currently don't have access to a Mac so I can't test it, but feel free to make the edit and I'll accept.

– Will
Dec 29 '14 at 17:48

2

I've installed freetds via brew install freetds --with-unixodbc, and pymssql via pip install pymssql. Then pymssql works well in python

– cdarlint
Jun 10 '15 at 5:25

2

New tarballs don't include iodbc anymore, so you should be able to skip that step now.

– nerdwaller
May 2 '16 at 13:35

Nice answer! I just did a LOT of searching and finally got this working. I think you should change the order of those 11 steps. (Installing TDSServer before unixodbc) because we have to specify the driver in odbc ini file. Also, while installing pyodbc, I had to change the setting in setup.py for drivers from iodbc to odbc to make it use unixodbc, and then install it. You should update 2nd step with this step, and then I guess answer would be complete. :)

– Forbidden Overseer
Dec 26 '14 at 11:44

I currently don't have access to a Mac so I can't test it, but feel free to make the edit and I'll accept.

– Will
Dec 29 '14 at 17:48

I've installed freetds via brew install freetds --with-unixodbc, and pymssql via pip install pymssql. Then pymssql works well in python

– cdarlint
Jun 10 '15 at 5:25

New tarballs don't include iodbc anymore, so you should be able to skip that step now.

– nerdwaller
May 2 '16 at 13:35

add a comment |

I've been able to simplify this and repeatedly have it work in my environments as of May 2016:

Install FreeTDS

brew install freetds --with-unixodbc

Install PYODBC

Extrapolated from Reference

pip install -U 

    --global-option=build_ext 

    --global-option="-I/usr/local/include" 

    --global-option="-L/usr/local/lib" 

    pyodbc

Tell UnixODBC about the FreeTDS Driver

Note: You may have a different version

cat <<'EOF' >> /usr/local/Cellar/unixodbc/2.3.4/etc/odbcinst.ini

[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1

EOF

From there, I had to tell pyodbc to use the FreeTDS Driver:

dsn = 'DRIVER=FreeTDS;DATABASE=MyDb;SERVER=...'

This is fantastic as now you can use it with aioodbc if you are doing async programming in Python 3.x:

async with aioodbc.connect(dsn=dsn, loop=asyncio.get_event_loop()) as conn:

    async with conn.cursor() as cur:

        await cur.execute('SELECT 42')

        r = await cur.fetchall()

        print(r)

Alternatively: You can use pymssql flat out, but that won't work if you want to use odbc or asyncio.

edited May 23 '17 at 10:31

Community♦

answered May 2 '16 at 15:06

nerdwaller

1,2781318

add a comment |

I've been able to simplify this and repeatedly have it work in my environments as of May 2016:

Install FreeTDS

brew install freetds --with-unixodbc

Install PYODBC

Extrapolated from Reference

pip install -U 

    --global-option=build_ext 

    --global-option="-I/usr/local/include" 

    --global-option="-L/usr/local/lib" 

    pyodbc

Tell UnixODBC about the FreeTDS Driver

Note: You may have a different version

cat <<'EOF' >> /usr/local/Cellar/unixodbc/2.3.4/etc/odbcinst.ini

[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1

EOF

From there, I had to tell pyodbc to use the FreeTDS Driver:

dsn = 'DRIVER=FreeTDS;DATABASE=MyDb;SERVER=...'

This is fantastic as now you can use it with aioodbc if you are doing async programming in Python 3.x:

async with aioodbc.connect(dsn=dsn, loop=asyncio.get_event_loop()) as conn:

    async with conn.cursor() as cur:

        await cur.execute('SELECT 42')

        r = await cur.fetchall()

        print(r)

Alternatively: You can use pymssql flat out, but that won't work if you want to use odbc or asyncio.

edited May 23 '17 at 10:31

Community♦

answered May 2 '16 at 15:06

nerdwaller

1,2781318

add a comment |

I've been able to simplify this and repeatedly have it work in my environments as of May 2016:

Install FreeTDS

brew install freetds --with-unixodbc

Install PYODBC

Extrapolated from Reference

pip install -U 

    --global-option=build_ext 

    --global-option="-I/usr/local/include" 

    --global-option="-L/usr/local/lib" 

    pyodbc

Tell UnixODBC about the FreeTDS Driver

Note: You may have a different version

cat <<'EOF' >> /usr/local/Cellar/unixodbc/2.3.4/etc/odbcinst.ini

[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1

EOF

From there, I had to tell pyodbc to use the FreeTDS Driver:

dsn = 'DRIVER=FreeTDS;DATABASE=MyDb;SERVER=...'

This is fantastic as now you can use it with aioodbc if you are doing async programming in Python 3.x:

async with aioodbc.connect(dsn=dsn, loop=asyncio.get_event_loop()) as conn:

    async with conn.cursor() as cur:

        await cur.execute('SELECT 42')

        r = await cur.fetchall()

        print(r)

Alternatively: You can use pymssql flat out, but that won't work if you want to use odbc or asyncio.

edited May 23 '17 at 10:31

Community♦

answered May 2 '16 at 15:06

nerdwaller

1,2781318

I've been able to simplify this and repeatedly have it work in my environments as of May 2016:

Install FreeTDS

brew install freetds --with-unixodbc

Install PYODBC

Extrapolated from Reference

pip install -U 

    --global-option=build_ext 

    --global-option="-I/usr/local/include" 

    --global-option="-L/usr/local/lib" 

    pyodbc

Tell UnixODBC about the FreeTDS Driver

Note: You may have a different version

cat <<'EOF' >> /usr/local/Cellar/unixodbc/2.3.4/etc/odbcinst.ini

[FreeTDS]

Description=FreeTDS Driver for Linux & MSSQL on Win32

Driver=/usr/local/lib/libtdsodbc.so

Setup=/usr/local/lib/libtdsodbc.so

UsageCount=1

EOF

From there, I had to tell pyodbc to use the FreeTDS Driver:

dsn = 'DRIVER=FreeTDS;DATABASE=MyDb;SERVER=...'

This is fantastic as now you can use it with aioodbc if you are doing async programming in Python 3.x:

async with aioodbc.connect(dsn=dsn, loop=asyncio.get_event_loop()) as conn:

    async with conn.cursor() as cur:

        await cur.execute('SELECT 42')

        r = await cur.fetchall()

        print(r)

Alternatively: You can use pymssql flat out, but that won't work if you want to use odbc or asyncio.

edited May 23 '17 at 10:31

Community♦

answered May 2 '16 at 15:06

nerdwaller

1,2781318

edited May 23 '17 at 10:31

Community♦

edited May 23 '17 at 10:31

Community♦

edited May 23 '17 at 10:31

Community♦

answered May 2 '16 at 15:06

nerdwaller

1,2781318

answered May 2 '16 at 15:06

nerdwaller

1,2781318

answered May 2 '16 at 15:06

nerdwaller

1,2781318

add a comment |

Will's answer was really helpful to me.

Here are some notes on a couple differences I experienced along the way, in case they help others:

The pyodbc tarball already had the change required, so all I had to do was download it and run python setup.py install. (Note: The version I had installed with pip was still using iodbc, so that didn't work.

The Verify FreeTDS installed step didn't allow me to connect to the database because I don't have access to the master, and there is apparently no way to specify. This seems to be a well known issue. I wasted a bunch of time trying to solve it, but failed and in the end it didn't block other steps from working.

These instructions say to put the username and password in odbc.ini. Since we need to say the login credentials again when we log in, I tried removing the UserName and Password from odbc.ini, hoping they weren't really necessary. (I'd rather have my password written down in fewer places!) This worked fine.

I had to add the host to the userid in isql MYSERVER myname@foo.bar.com MYPASSWORD (and in the Python code).

(I hoped that this would mean I don't need the host in freetds.conf, but alas, that has to stay.)

edited Aug 15 '17 at 19:34

JakeGould

20.7k84975

answered May 21 '15 at 14:18

DavidC

764515

add a comment |

Will's answer was really helpful to me.

Here are some notes on a couple differences I experienced along the way, in case they help others:

The pyodbc tarball already had the change required, so all I had to do was download it and run python setup.py install. (Note: The version I had installed with pip was still using iodbc, so that didn't work.

The Verify FreeTDS installed step didn't allow me to connect to the database because I don't have access to the master, and there is apparently no way to specify. This seems to be a well known issue. I wasted a bunch of time trying to solve it, but failed and in the end it didn't block other steps from working.

These instructions say to put the username and password in odbc.ini. Since we need to say the login credentials again when we log in, I tried removing the UserName and Password from odbc.ini, hoping they weren't really necessary. (I'd rather have my password written down in fewer places!) This worked fine.

I had to add the host to the userid in isql MYSERVER myname@foo.bar.com MYPASSWORD (and in the Python code).

(I hoped that this would mean I don't need the host in freetds.conf, but alas, that has to stay.)

edited Aug 15 '17 at 19:34

JakeGould

20.7k84975

answered May 21 '15 at 14:18

DavidC

764515

add a comment |

Will's answer was really helpful to me.

Here are some notes on a couple differences I experienced along the way, in case they help others:

The pyodbc tarball already had the change required, so all I had to do was download it and run python setup.py install. (Note: The version I had installed with pip was still using iodbc, so that didn't work.

The Verify FreeTDS installed step didn't allow me to connect to the database because I don't have access to the master, and there is apparently no way to specify. This seems to be a well known issue. I wasted a bunch of time trying to solve it, but failed and in the end it didn't block other steps from working.

These instructions say to put the username and password in odbc.ini. Since we need to say the login credentials again when we log in, I tried removing the UserName and Password from odbc.ini, hoping they weren't really necessary. (I'd rather have my password written down in fewer places!) This worked fine.

I had to add the host to the userid in isql MYSERVER myname@foo.bar.com MYPASSWORD (and in the Python code).

(I hoped that this would mean I don't need the host in freetds.conf, but alas, that has to stay.)

edited Aug 15 '17 at 19:34

JakeGould

20.7k84975

answered May 21 '15 at 14:18

DavidC

764515

Will's answer was really helpful to me.

Here are some notes on a couple differences I experienced along the way, in case they help others:

The pyodbc tarball already had the change required, so all I had to do was download it and run python setup.py install. (Note: The version I had installed with pip was still using iodbc, so that didn't work.

The Verify FreeTDS installed step didn't allow me to connect to the database because I don't have access to the master, and there is apparently no way to specify. This seems to be a well known issue. I wasted a bunch of time trying to solve it, but failed and in the end it didn't block other steps from working.

These instructions say to put the username and password in odbc.ini. Since we need to say the login credentials again when we log in, I tried removing the UserName and Password from odbc.ini, hoping they weren't really necessary. (I'd rather have my password written down in fewer places!) This worked fine.

I had to add the host to the userid in isql MYSERVER myname@foo.bar.com MYPASSWORD (and in the Python code).

(I hoped that this would mean I don't need the host in freetds.conf, but alas, that has to stay.)

edited Aug 15 '17 at 19:34

JakeGould

20.7k84975

answered May 21 '15 at 14:18

DavidC

764515

edited Aug 15 '17 at 19:34

JakeGould

20.7k84975

edited Aug 15 '17 at 19:34

JakeGould

20.7k84975

edited Aug 15 '17 at 19:34

JakeGould

20.7k84975

answered May 21 '15 at 14:18

DavidC

764515

answered May 21 '15 at 14:18

DavidC

764515

answered May 21 '15 at 14:18

DavidC

764515

add a comment |

I am on macOS Sierra 10.12.3. pymssql did the job perfectly. If nothing works from other upvoted answers, follow this:

brew unlink freetds

brew install homebrew/versions/freetds091

pip install pymssql

and here is a sample snippet to establish connection:

conn = pymssql.connect(serverhostname, username, password, dbname)

cursor = conn.cursor()

cursor.execute('SELECT * FROM users')

answered Feb 6 '17 at 5:09

intrepidkarthi

2,21083473

add a comment |

I am on macOS Sierra 10.12.3. pymssql did the job perfectly. If nothing works from other upvoted answers, follow this:

brew unlink freetds

brew install homebrew/versions/freetds091

pip install pymssql

and here is a sample snippet to establish connection:

conn = pymssql.connect(serverhostname, username, password, dbname)

cursor = conn.cursor()

cursor.execute('SELECT * FROM users')

answered Feb 6 '17 at 5:09

intrepidkarthi

2,21083473

add a comment |

I am on macOS Sierra 10.12.3. pymssql did the job perfectly. If nothing works from other upvoted answers, follow this:

brew unlink freetds

brew install homebrew/versions/freetds091

pip install pymssql

and here is a sample snippet to establish connection:

conn = pymssql.connect(serverhostname, username, password, dbname)

cursor = conn.cursor()

cursor.execute('SELECT * FROM users')

answered Feb 6 '17 at 5:09

intrepidkarthi

2,21083473

I am on macOS Sierra 10.12.3. pymssql did the job perfectly. If nothing works from other upvoted answers, follow this:

brew unlink freetds

brew install homebrew/versions/freetds091

pip install pymssql

and here is a sample snippet to establish connection:

conn = pymssql.connect(serverhostname, username, password, dbname)

cursor = conn.cursor()

cursor.execute('SELECT * FROM users')

answered Feb 6 '17 at 5:09

intrepidkarthi

2,21083473

answered Feb 6 '17 at 5:09

intrepidkarthi

2,21083473

answered Feb 6 '17 at 5:09

intrepidkarthi

2,21083473

answered Feb 6 '17 at 5:09

intrepidkarthi

2,21083473

add a comment |

Pyodbc + MS's own odbc provider, msodbcsql, rather than FreeTDS. My reasoning was simple - who is most motivated to have good SQL Server support? MS.

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-connect-query-python

(venv) jluc@sandbox$ brew list

 msodbcsql  openssl     unixodbc

Connect string that worked for me:

Driver={ODBC Driver 13 for SQL Server};Server=192.168.1.xxx;Database=mydb;Uid=myuser;Pwd=mypassword;

And, for SQL Alchemy:

"mssql+pyodbc://%(user)s:%(password)s@%(hostname)s:%(port)s/%(dbname)s?driver=ODBC+Driver+13+for+SQL+Server"

Versions: Sierra, Python 2.7, SQL Server 2016 Dev edition, Win 10 Pro.

Note: be careful around MS’s brew install. I think it used to take the initiative to install Homebrew. Not sure if it would’ve been an issue in practice.

edited Nov 22 '18 at 6:55

answered Jun 27 '17 at 20:53

JL Peyret

3,0951630

Going to route of installing the Microsoft ODBC drivers fixed the issue for me. Good suggestions here: superuser.com/questions/1355732/…

– Snympi
Nov 21 '18 at 14:19

add a comment |

Pyodbc + MS's own odbc provider, msodbcsql, rather than FreeTDS. My reasoning was simple - who is most motivated to have good SQL Server support? MS.

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-connect-query-python

(venv) jluc@sandbox$ brew list

 msodbcsql  openssl     unixodbc

Connect string that worked for me:

Driver={ODBC Driver 13 for SQL Server};Server=192.168.1.xxx;Database=mydb;Uid=myuser;Pwd=mypassword;

And, for SQL Alchemy:

"mssql+pyodbc://%(user)s:%(password)s@%(hostname)s:%(port)s/%(dbname)s?driver=ODBC+Driver+13+for+SQL+Server"

Versions: Sierra, Python 2.7, SQL Server 2016 Dev edition, Win 10 Pro.

Note: be careful around MS’s brew install. I think it used to take the initiative to install Homebrew. Not sure if it would’ve been an issue in practice.

edited Nov 22 '18 at 6:55

answered Jun 27 '17 at 20:53

JL Peyret

3,0951630

Going to route of installing the Microsoft ODBC drivers fixed the issue for me. Good suggestions here: superuser.com/questions/1355732/…

– Snympi
Nov 21 '18 at 14:19

add a comment |

Pyodbc + MS's own odbc provider, msodbcsql, rather than FreeTDS. My reasoning was simple - who is most motivated to have good SQL Server support? MS.

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-connect-query-python

(venv) jluc@sandbox$ brew list

 msodbcsql  openssl     unixodbc

Connect string that worked for me:

Driver={ODBC Driver 13 for SQL Server};Server=192.168.1.xxx;Database=mydb;Uid=myuser;Pwd=mypassword;

And, for SQL Alchemy:

"mssql+pyodbc://%(user)s:%(password)s@%(hostname)s:%(port)s/%(dbname)s?driver=ODBC+Driver+13+for+SQL+Server"

Versions: Sierra, Python 2.7, SQL Server 2016 Dev edition, Win 10 Pro.

Note: be careful around MS’s brew install. I think it used to take the initiative to install Homebrew. Not sure if it would’ve been an issue in practice.

edited Nov 22 '18 at 6:55

answered Jun 27 '17 at 20:53

JL Peyret

3,0951630

Pyodbc + MS's own odbc provider, msodbcsql, rather than FreeTDS. My reasoning was simple - who is most motivated to have good SQL Server support? MS.

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-connect-query-python

(venv) jluc@sandbox$ brew list

 msodbcsql  openssl     unixodbc

Connect string that worked for me:

Driver={ODBC Driver 13 for SQL Server};Server=192.168.1.xxx;Database=mydb;Uid=myuser;Pwd=mypassword;

And, for SQL Alchemy:

"mssql+pyodbc://%(user)s:%(password)s@%(hostname)s:%(port)s/%(dbname)s?driver=ODBC+Driver+13+for+SQL+Server"

Versions: Sierra, Python 2.7, SQL Server 2016 Dev edition, Win 10 Pro.

Note: be careful around MS’s brew install. I think it used to take the initiative to install Homebrew. Not sure if it would’ve been an issue in practice.

edited Nov 22 '18 at 6:55

answered Jun 27 '17 at 20:53

JL Peyret

3,0951630

edited Nov 22 '18 at 6:55

answered Jun 27 '17 at 20:53

JL Peyret

3,0951630

answered Jun 27 '17 at 20:53

JL Peyret

3,0951630

answered Jun 27 '17 at 20:53

JL Peyret

3,0951630

Going to route of installing the Microsoft ODBC drivers fixed the issue for me. Good suggestions here: superuser.com/questions/1355732/…

– Snympi
Nov 21 '18 at 14:19

add a comment |

Going to route of installing the Microsoft ODBC drivers fixed the issue for me. Good suggestions here: superuser.com/questions/1355732/…

– Snympi
Nov 21 '18 at 14:19

Going to route of installing the Microsoft ODBC drivers fixed the issue for me. Good suggestions here: superuser.com/questions/1355732/…

– Snympi
Nov 21 '18 at 14:19

add a comment |

There are a lot of hoops to jump through. Will's answer outlines a good number of them.

After much struggle, I managed to get this working with Docker (so this should work anywhere that runs docker).

I have tested the setup with Python 3.6 and Python 2.7: with pyodbc==3.0.10, django-pyodbc-azure and Django 1.10.4 (this setup is for Django, but works for vanilla python as well).

I've created a public image which you can use: https://hub.docker.com/r/toast38coza/python-mssql/

Here is a simple working docker setup:

version: "3"

services:

  db:

    restart: on-failure:10

    image: microsoft/mssql-server-linux:latest

    environment:

      - ACCEPT_EULA=Y

      - SA_PASSWORD=SuperSecret(!)100

    ports:

      - "1433:1433"

  py:

    image: toast38coza/python-mssql

    links:

      - db

    environment:

      - SA_PASSWORD=SuperSecret(!)100

      - DB_NAME=mydb

Now you can run:

docker-compose run --rm py python

Which will run the python cli inside the py service above

Then try create a database:

>>> import pyodbc, os

>>> db_name = os.environ.get('DB_NAME')

>>> pwd = os.environ.get('SA_PASSWORD')

>>> connection_string = "driver=FreeTDS;server=db;PORT=1433 database=master;UID=sa;PWD={};TDS_Version=8.0;".format(pwd)

>>> conn = pyodbc.connect(connection_string, autocommit=True)

>>> conn.execute('create database {}'.format(db_name))

<pyodbc.Cursor object at 0x7fb3067f0e70>

If you're using Django, there is a more complete example in the repo, but, just a heads up, you will need your settings to look something like this:

DATABASES = {

    'default': {

        'ENGINE': "sql_server.pyodbc",

        'HOST': "db",

        'PORT':'1433',

        'USER': "sa",

        'PASSWORD': os.environ.get('SA_PASSWORD'),

        'NAME': os.environ.get('DB_NAME'),

        'OPTIONS': {

            "driver": "FreeTDS",

            "host_is_server": True,

            "unicode_results": True,

            "extra_params": "tds_version=8.0",

        }

    }

}

answered Apr 11 '17 at 10:28

toast38coza

4,87313025

add a comment |

There are a lot of hoops to jump through. Will's answer outlines a good number of them.

After much struggle, I managed to get this working with Docker (so this should work anywhere that runs docker).

I have tested the setup with Python 3.6 and Python 2.7: with pyodbc==3.0.10, django-pyodbc-azure and Django 1.10.4 (this setup is for Django, but works for vanilla python as well).

I've created a public image which you can use: https://hub.docker.com/r/toast38coza/python-mssql/

Here is a simple working docker setup:

version: "3"

services:

  db:

    restart: on-failure:10

    image: microsoft/mssql-server-linux:latest

    environment:

      - ACCEPT_EULA=Y

      - SA_PASSWORD=SuperSecret(!)100

    ports:

      - "1433:1433"

  py:

    image: toast38coza/python-mssql

    links:

      - db

    environment:

      - SA_PASSWORD=SuperSecret(!)100

      - DB_NAME=mydb

Now you can run:

docker-compose run --rm py python

Which will run the python cli inside the py service above

Then try create a database:

>>> import pyodbc, os

>>> db_name = os.environ.get('DB_NAME')

>>> pwd = os.environ.get('SA_PASSWORD')

>>> connection_string = "driver=FreeTDS;server=db;PORT=1433 database=master;UID=sa;PWD={};TDS_Version=8.0;".format(pwd)

>>> conn = pyodbc.connect(connection_string, autocommit=True)

>>> conn.execute('create database {}'.format(db_name))

<pyodbc.Cursor object at 0x7fb3067f0e70>

If you're using Django, there is a more complete example in the repo, but, just a heads up, you will need your settings to look something like this:

DATABASES = {

    'default': {

        'ENGINE': "sql_server.pyodbc",

        'HOST': "db",

        'PORT':'1433',

        'USER': "sa",

        'PASSWORD': os.environ.get('SA_PASSWORD'),

        'NAME': os.environ.get('DB_NAME'),

        'OPTIONS': {

            "driver": "FreeTDS",

            "host_is_server": True,

            "unicode_results": True,

            "extra_params": "tds_version=8.0",

        }

    }

}

answered Apr 11 '17 at 10:28

toast38coza

4,87313025

add a comment |

There are a lot of hoops to jump through. Will's answer outlines a good number of them.

After much struggle, I managed to get this working with Docker (so this should work anywhere that runs docker).

I have tested the setup with Python 3.6 and Python 2.7: with pyodbc==3.0.10, django-pyodbc-azure and Django 1.10.4 (this setup is for Django, but works for vanilla python as well).

I've created a public image which you can use: https://hub.docker.com/r/toast38coza/python-mssql/

Here is a simple working docker setup:

version: "3"

services:

  db:

    restart: on-failure:10

    image: microsoft/mssql-server-linux:latest

    environment:

      - ACCEPT_EULA=Y

      - SA_PASSWORD=SuperSecret(!)100

    ports:

      - "1433:1433"

  py:

    image: toast38coza/python-mssql

    links:

      - db

    environment:

      - SA_PASSWORD=SuperSecret(!)100

      - DB_NAME=mydb

Now you can run:

docker-compose run --rm py python

Which will run the python cli inside the py service above

Then try create a database:

>>> import pyodbc, os

>>> db_name = os.environ.get('DB_NAME')

>>> pwd = os.environ.get('SA_PASSWORD')

>>> connection_string = "driver=FreeTDS;server=db;PORT=1433 database=master;UID=sa;PWD={};TDS_Version=8.0;".format(pwd)

>>> conn = pyodbc.connect(connection_string, autocommit=True)

>>> conn.execute('create database {}'.format(db_name))

<pyodbc.Cursor object at 0x7fb3067f0e70>

If you're using Django, there is a more complete example in the repo, but, just a heads up, you will need your settings to look something like this:

DATABASES = {

    'default': {

        'ENGINE': "sql_server.pyodbc",

        'HOST': "db",

        'PORT':'1433',

        'USER': "sa",

        'PASSWORD': os.environ.get('SA_PASSWORD'),

        'NAME': os.environ.get('DB_NAME'),

        'OPTIONS': {

            "driver": "FreeTDS",

            "host_is_server": True,

            "unicode_results": True,

            "extra_params": "tds_version=8.0",

        }

    }

}

answered Apr 11 '17 at 10:28

toast38coza

4,87313025

There are a lot of hoops to jump through. Will's answer outlines a good number of them.

After much struggle, I managed to get this working with Docker (so this should work anywhere that runs docker).

I have tested the setup with Python 3.6 and Python 2.7: with pyodbc==3.0.10, django-pyodbc-azure and Django 1.10.4 (this setup is for Django, but works for vanilla python as well).

I've created a public image which you can use: https://hub.docker.com/r/toast38coza/python-mssql/

Here is a simple working docker setup:

version: "3"

services:

  db:

    restart: on-failure:10

    image: microsoft/mssql-server-linux:latest

    environment:

      - ACCEPT_EULA=Y

      - SA_PASSWORD=SuperSecret(!)100

    ports:

      - "1433:1433"

  py:

    image: toast38coza/python-mssql

    links:

      - db

    environment:

      - SA_PASSWORD=SuperSecret(!)100

      - DB_NAME=mydb

Now you can run:

docker-compose run --rm py python

Which will run the python cli inside the py service above

Then try create a database:

>>> import pyodbc, os

>>> db_name = os.environ.get('DB_NAME')

>>> pwd = os.environ.get('SA_PASSWORD')

>>> connection_string = "driver=FreeTDS;server=db;PORT=1433 database=master;UID=sa;PWD={};TDS_Version=8.0;".format(pwd)

>>> conn = pyodbc.connect(connection_string, autocommit=True)

>>> conn.execute('create database {}'.format(db_name))

<pyodbc.Cursor object at 0x7fb3067f0e70>

If you're using Django, there is a more complete example in the repo, but, just a heads up, you will need your settings to look something like this:

DATABASES = {

    'default': {

        'ENGINE': "sql_server.pyodbc",

        'HOST': "db",

        'PORT':'1433',

        'USER': "sa",

        'PASSWORD': os.environ.get('SA_PASSWORD'),

        'NAME': os.environ.get('DB_NAME'),

        'OPTIONS': {

            "driver": "FreeTDS",

            "host_is_server": True,

            "unicode_results": True,

            "extra_params": "tds_version=8.0",

        }

    }

}

answered Apr 11 '17 at 10:28

toast38coza

4,87313025

answered Apr 11 '17 at 10:28

toast38coza

4,87313025

answered Apr 11 '17 at 10:28

toast38coza

4,87313025

answered Apr 11 '17 at 10:28

toast38coza

4,87313025

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu

SQL Server, Python, and OS X

7 Answers
7

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Your Answer

Post as a guest

7 Answers
7

7 Answers
7

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Post as a guest

Popular posts from this blog

MongoDB - Not Authorized To Execute Command

Npm cannot find a required file even through it is in the searched directory

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

Category

Random preview

SQL Server, Python, and OS X

7 Answers 7

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Your Answer

Sign up or log in

Post as a guest

Post as a guest

7 Answers 7

7 Answers 7

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Install FreeTDS

Install PYODBC

Tell UnixODBC about the FreeTDS Driver

Sign up or log in

Post as a guest

Post as a guest

Sign up or log in

Post as a guest

Sign up or log in

Post as a guest

Sign up or log in

Post as a guest

Popular posts from this blog

MongoDB - Not Authorized To Execute Command

Npm cannot find a required file even through it is in the searched directory

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

7 Answers
7

7 Answers
7

7 Answers
7