pyodbc

I am trying to write results of some processing into SQL Server table. My results are store in a list of lists where each item of the list is a list. I am using parameters (6 params) and I am getting the following error: cnxn.execute(sqlStatement, (item[0],item[1],item[2],item[3],item[4],item[5])) pyodbc.ProgrammingError: ('The SQL contains 0 parameter markers, but 6 parameters were supplied', 'HY000') That's my code sqlStatement = "INSERT INTO CEA_CR (`SessionID`, `Session.Call_TYPE_Assigned`, `Session.Did_Call_Type_happen_on_this_call`, `Session.Was_there_a_system_or_Rep_generated_Memo_that

I just downloaded installer for pyodbc from google project . I have Python 3.5 istalled and pyodbc requires 3.3. Is there an easy work around? P.S. I am installing it on PC without Internet access. This is for Windows. Since you can't install this via the regular pip channels, you can download a prebuilt binary for Python 3.5 from Chris Gohlke's site , where he has a bunch of libraries he creates builds for. Download either depending on the version of Python 3.5 you have installed: pyodbc‑3.0.10‑cp35‑none‑win32.whl if you have a 32-bit Python 3.5 install pyodbc‑3.0.10‑cp35‑none‑win_amd64.whl

As far as i can understand to use pyodbc you have to cnxn = pyodbc.connect('DRIVER={Advantage ODBC Driver};SERVER=local;DataDirectory=\\AltaDemo\Demo\AltaPoint.add;DATABASE=AltaPoint;UID=admin;PWD=admin;ServerTypes=1;') cursor = cnxn.cursor() This is the error i get from the console when i run this Error: ('IM002', '[IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified (0) (SQLDriverConnect)') The name of the driver is Advantage StreamlineSQL ODBC , so the bare minimum connect string is: DRIVER={Advantage StreamlineSQL ODBC};DataDirectory=D:\Temp

I'm having the same problem as this guy and possibly this guy , but I am around to share some code and respond to questions! I have some code in a batch job that reads fields from a Microsoft Access database via pyodbc and prepares the output for display. Here is a snippet. Note the assert. def format_currency(amount): if amount is None: return "" else: result = "$%.2f" % amount assert ":" not in result, ( "That's weird. The value %r of class %s is represented as %s" % (amount, amount.__class__, result)) return result When I run it, it successfully processes 100,000 rows and then fails:

I'm trying to create a SQL Server database using pyodbc. import pyodbc server = 'AMR112\NAMED1' database = 'msdb' username = '' password = 'mypassword' abcd='yes' ghi='False' #driver = '{/usr/local/lib/libtdsodbc.so}' #for linux of windows driver= '{ODBC Driver 13 for SQL Server}' cnxn = pyodbc.connect('DRIVER='+driver+';PORT=1433;SERVER='+server+??';PORT=1443;DATABASE??='+database+';UID='+??username+';PWD='+ password+';trusted_connection='+ abcd+'; autocommit='+ ghi) cursor = cnxn.cursor() cursor.execute("create database dbafgh") row = cursor.fetchone() if row: print row cursor.close() It

Background: i have been at it for about a week but still no luck. the same driver (13.0) on my system (Ubuntu 16.04.1 LTS) works just fine with my pyodbc python (Python 2.7.12 :: Anaconda 4.1.1 (64-bit)) library. i tried setting up a virtual machine on AWS E2 but it does not work there as described below. Objective: Connect to Azure SQL Server using Python 2.7.12 :: Anaconda 4.2.0 (64-bit) with official ODBC Driver from Microsoft on Amazon Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-53-generic x86_64) Problem: I have tried connecting pyodbc to azure sql using the ODBC official ODBC driver 13 from

I'm using pyodbc to query to an SQL Server database import datetime import pyodbc conn = pyodbc.connect("Driver={SQL Server};Server='dbserver',Database='db', TrustedConnection=Yes") cursor = conn.cursor() ratings = ("PG-13", "PG", "G") st_dt = datetime(2010, 1, 1) end_dt = datetime(2010, 12, 31) cursor.execute("""Select title, director, producer From movies Where rating In ? And release_dt Between ? And ?""", ratings, str(st_dt), str(end_dt)) but am receiving the error below. Does the tuple parameter need to be handled in a different way? Is there a better way to structure this query? ('42000'