Skip to main content

Connecting to SQL Server with pyodbc

At long last after my previous posts on this topic we get to the easy part: using pyodbc to run queries against SQL Server.

If you need to get caught up, the posts you'll want to go through before proceeding with this one are:

With a datasource created in unixODBC this last part is rather anti-climactic, but this is of course also where you can get some real work done in Python.

First, in a Python console ('python' from a terminal or whatever your favorite Python console tool is), import pyodbc:
>>> import pyodbc

Next, create a connection to the datasource using the datasource name, which in this case we'll assume is foo:
>>> conn = pyodbc.connect('DSN=foo;UID=username;PWD=password')

If you don't get any errors, the connection was successful. Next, create a cursor on that connection:
>>> cursor = conn.cursor()

Now we can execute a query against SQL Server using that cursor:
>>> cursor.execute("SELECT * FROM bar")

If the query ran successfully, you'll see that a pyodbc.Cursor object is returned:
<pyodbc.Cursor object at 0x15a5a50>

Next, and this is is not the most efficient way to do things (see below) but is good for demonstration purposes, let's call fetachall() on the cursor and set that to a variable called rows:
>>> rows = cursor.fetchall()

This returns a list of pyodbc Row objects, which are basically tuples.

Finally, we can iterate on the Cursor and output the results of the query:
for row in rows:
    print row


This will output each row so you can see the results of your handiwork.

That's all there is to it!

Of course there are a lot of ways to get at the individual column values returned from the query, so be sure and check out the pyodbc Getting Started wiki for details.

Note that there are numerous considerations depending on the volume and nature of data with which you're dealing. For example if you have a large amount of data, using fetchall() isn't advisable since that will load all the results into memory, so you'll probably much more commonly want to use fetchone() in a loop instead since that's much more memory efficient.

You can learn all about the objects, methods, etc. involved with pyodbc in the pyodbc wiki.

Next up is pymssql!


Comments

Jason Wohlford said…
Thanks, Matt. Those were some very helpful posts. You got me from FreeTDS -> unixODBC -> pyodbc in one easy morning. Much appreciated!
Matt Woodward said…
Glad you found it helpful!
Яблоков said…
Found these posts the most helpful of the whole web. Scary theme became clear!
Daniel Addyson said…
great intro to this. thanks for sharing.
Rob said…
This was extremely helpful in resolving MSSQL and django connection issues. Thanks a bunch!

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…