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!
Thanks foe sharing info on Connecting to SQL Server with pyodbc

Popular posts from this blog

Running a Django Application on Windows Server 2012 with IIS

This is a first for me since under normal circumstances we run all our Django applications on Linux with Nginx, but we're in the process of developing an application for another department and due to the requirements around this project, we'll be handing the code off to them to deploy. They don't have any experience with Linux or web servers other than IIS, so I recently took up the challenge of figuring out how to run Django applications on Windows Server 2012 with IIS.

Based on the dated or complete lack of information around this I'm assuming it's not something that's very common in the wild, so I thought I'd share what I came up with in case others need to do this.


This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Assumptions and CaveatsThe operating system is Windows Server 2012 R2, 64-bit. If another variant of the operating system is being used, these instructions may not work properly.All of the soft…

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 …

Fixing DPI Scaling Issues in Skype for Business on Windows 10

My setup for my day job these days is a Surface Pro 4 and either an LG 34UC87M-B or a Dell P2715Q monitor, depending on where I'm working. This is a fantastic setup, but some applications have trouble dealing with the high pixel density and don't scale appropriately.
One case in point is Skype for Business. For some reason it scales correctly as I move between the Surface screen and the external monitor when I use the Dell, but on the LG monitor Skype is either massive on the external monitor, or tiny on the Surface screen.
After a big of digging around I came across a solution that worked for me, which is to change a setting in Skype's manifest file (who knew there was one?). On my machine the file is here: C:\Program Files\Microsoft Office\Office16\LYNC.EXE.MANIFEST
And the setting in question is this:
<dpiAware>True/PM</dpiAware>
Which I changed to this: <dpiAware>False/PM</dpiAware>
Note that you'll probably have to edit the file as administr…