Hi Rick,
This could involve quite a bit of investigation on our part, so it
could take a while before we get to the bottom of it.
We're running Windows 2003 as the OS, MS SQL Server 2005, via the SQL
Server Native Driver, using PYODBC, Apache 2.2.6 mod_python 3.3.1.
The app is based on Pylons,
Hi Bruce,
I'm considering a switch from pymssql to pyodbc myself in the
not-too-distance future, and this thread has me a bit curious about what's
going on. This is a subject that may affect SQL more in the future when ODBC
and JDBC drivers get more use.
I think there's two distinct questions
Thanks for your speedy response Michael :)
Yes, after more searching it does rather look like this is an issue
that has to do with MSSQL, rather than SQLA. This post (http://
forums.microsoft.com/MSDN/ShowPost.aspx?PostID=570896SiteID=1) seems
to point to a similar opinion, points the finger at
Just to be a bit more specific, these are the changes we will try in
our mssql db:
ALTER DATABASE MyDBName
SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE MyDBName
SET READ_COMMITTED_SNAPSHOT ON
:)
On May 14, 4:36 pm, BruceC [EMAIL PROTECTED] wrote:
Thanks for your speedy response Michael :)
On May 13, 2008, at 9:46 PM, BruceC wrote:
Hi all. I'm running a Pylons App using SA, Elixir connecting to a SQL
Server 2005 db via PYODBC. I'm getting a lot of database locks, the
statements appear to be like this:
SET FMTONLY ON select table1.id from table1 where 1=2 SET FMTONLY OFF
I
