[egenix-users] SQL Server: Experimental Solution

[M.-A. Lemburg]

nwingfield at che-llp.com wrote:
> We have been experiencing many problems with mxODBC and SQL Server, similar
> to those expressed by others list members (Sébastien Walgraffe, Peter
> Sabaini).  The most common error is this:
> 'HY000', 0, '[Microsoft][ODBC SQL Server Driver]Connection is busy with
> results for another hstmt', 5911
> By eliminating Z SQL methods, we seem to have remedied this error, though
> only time will tell.  We have replaced Z SQL methods with the External
> Method that I am including below.  Another problem that we experienced was
> that when the connection pool was set greater than one, pages executing
> multiple SQL statements could lock up.  This is because each SQL method was
> potentially executed on a different connection.  Rather than limit
> ourselves to a connection pool of one, we incorporated some logic into the
> aforementioned method to maintain one connection per request.  If the
> locking isn't a problem for you, you can strip the extra logic out of this
> method.
> 
> Let me know if this helps.

If this does solve your problems, we'll add a connection option to the
Zope DA which will let you switch on/off this behaviour (grouping
connections per request) for version 1.0.7.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Software directly from the Source  (#1, Oct 23 2003)
 >>> Python/Zope Products & Consulting ...         http://www.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::