[sqlalchemy] Re: Adding with (nolock) to all queries (mssql)

2007-02-12 Thread Michael Bayer
On Feb 12, 4:25 am, Arnar Birgisson [EMAIL PROTECTED] wrote: Hi again, Yes, we thought that might be the case. We tried changing the isolation level on this connection to snapshot. Now I'm getting different errors, and more frequent. One error I get is this: AttributeError:

[sqlalchemy] Re: Adding with (nolock) to all queries (mssql)

2007-02-09 Thread Michael Bayer
before I read the next 10 replies in this thread, this seems like an issue of too high of a transaction isolation level going on (something that plagued my SQL server apps when i was writing them, though that was years ago). cant the connection itself have a more lenient isolation level set ?

[sqlalchemy] Re: Adding with (nolock) to all queries (mssql)

2007-02-08 Thread Rick Morrison
Pymssql, or adodbapi? Client-side cursors, or Server-side? We use pymssql here over FreeTDS with SQL Server 2005 here without issues. If your DBA suggests with (nolock), I'm assuming that you're seeing some sort of persistent table/page locks? Can you give a bit more info? On 2/8/07, Arnar

[sqlalchemy] Re: Adding with (nolock) to all queries (mssql)

2007-02-08 Thread Arnar Birgisson
Hi Rick, On 2/8/07, Rick Morrison [EMAIL PROTECTED] wrote: Pymssql, or adodbapi? Client-side cursors, or Server-side? Pymssql and client side cursors (I guess, I'm just issuing plain select statements, no stored procs or such). We use pymssql here over FreeTDS with SQL Server 2005 here

[sqlalchemy] Re: Adding with (nolock) to all queries (mssql)

2007-02-08 Thread Rick Morrison
Pymssql runs on top of the ancient library DB-lib, which has real issues with not fully reading all query results -- make sure all your query results are fully consumed, i.e. read them into a list and the iterate that instead of partially iterating the cursor. On 2/8/07, Arnar Birgisson [EMAIL

[sqlalchemy] Re: Adding with (nolock) to all queries (mssql)

2007-02-08 Thread Arnar Birgisson
Ok. Should I rather be using adodbapi then? Arnar On 2/8/07, Rick Morrison [EMAIL PROTECTED] wrote: Pymssql runs on top of the ancient library DB-lib, which has real issues with not fully reading all query results -- make sure all your query results are fully consumed, i.e. read them into a

[sqlalchemy] Re: Adding with (nolock) to all queries (mssql)

2007-02-08 Thread Rick Morrison
If you're using FreeTDS, I assume you're on some kind of Unix. As far as I know, adodbapi is Windows-only (anyway, it has its own set of idiosyncrasies too). On 2/8/07, Arnar Birgisson [EMAIL PROTECTED] wrote: Ok. Should I rather be using adodbapi then? Arnar On 2/8/07, Rick Morrison

[sqlalchemy] Re: Adding with (nolock) to all queries (mssql)

2007-02-08 Thread Rick Morrison
Yeah sorry, I should have caught that. On the pymssql vs. adodbapi, the answer is not an easy question, and is quite a mixed bag. MS supports ADO (at least for now), and no longer supports DB-Lib, so from that standpoint adodbapi would be the way to go, at least as regards the toolchain from