My favorites | Sign in
Project Home Downloads Wiki
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 81: exception when inserting more than 400KB in column
1 person starred this issue and may be notified of changes. Back to list
Status:  WontFix
Owner:  ----
Closed:  Dec 2009


 
Reported by alexandr...@gmail.com, Dec 15, 2009
What steps will reproduce the problem?

I'm using the latest release of pyodbc to connect to SQLServer 2005. 

I have attached a test case, which basically does the following

1. create 2 tables the first with a column of type varbinary(max) the other
with a column of type varchar(max).
2. insert data of increasing size (400kB-10 to 400kB+10)


What is the expected output? What do you see instead?

The tests should pass, however they fail with a data size of 400kB, with an
exception message:

HY000 / The driver did not supply a message. 

What version of the product are you using? On what operating system?

pyodbc 2.1.6 on python 2.5, running on Windows 2003 SP2. Connecting to
SQLServer 2005 using the SQL Native Client driver (version 9.00.4035.00)

Please provide any additional information below.

I'm not an ODBC expert. The research I've made on MSDN indicates that the
400k barrier is well known with ODBC, and that there is something called
Data-at-Execution which is supposed to be used to deal with it. I'm not yet
sure how this works, but I'll dig further into this. 

Many thanks for sharing pyodbc with the community. 

Alexandre
pyodbc_issue.py
1.9 KB   View   Download
Dec 22, 2009
Project Member #1 mkleehammer
Some good news.  I've found your test works with SQL Server 2008 using native client 10.0:

  DRIVER={SQL Server Native Client 10.0}

The problem is we don't yet know if the fix is in (1) SQL Server 2008 or (2) Native Client 10.0. 

We do know Native Client 10 can connect to SQL 2005, and I'm pretty sure you can download the client portion 
for free.  Since I don't have 2005 handy at home, can you test the Native Client 10 with 2005 if you can find a 
download?

In the meantime, I'll keep looking.

Status: Investigating
Dec 30, 2009
#2 alexandr...@gmail.com
Everything works fine with Native Client 10.0, so this looks like a driver issue. 

Using Native Client 10.0 is definitely a solution for me, so as far as I'm concerned
everything is fine. I have no idea if this deserves reporting to Microsoft (and how
this can be achieved...). 
Dec 31, 2009
Project Member #3 mkleehammer
(No comment was entered for this change.)
Status: WontFix

Powered by Google Project Hosting