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 <[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 list and the > > iterate that instead of partially iterating the cursor. > > > > > > > > On 2/8/07, Arnar Birgisson <[EMAIL PROTECTED]> wrote: > > > > > > 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 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? > > > > > > I'm trying to analyze the problem right now, but I'm afraid I don't > > > have alot of info. We were having locking issues in other systems > > > running of the same db server which were solved (partially at least) > > > by adding nolock hints to datawarehousing procedures. > > > > > > The symptom on the SA side is that this seems to happen after the > > > server (apache/mod_python) has been running for a while. A user (and > > > always the same two out of ~40) call me and says his page is empty - > > > meaning that the main query is giving 0 result rows when it should be > > > giving >300. I log in with my name and everything is fine - I log in > > > with his and I see the empty screen. If I restart apache it fixes the > > > problem for a while. > > > > > > I don't see any errors or tracebacks in the apache error_log, but I > > > have yet to enable more logging since this only happens on the > > > production server and quite sporadically. > > > > > > This has some pre-history. I was initially running this in cherrypy > > > which was simply not working at all. DB connections would lock up > > > until there were no left in the pool and this happend quite fast, in > > > about 20 minutes. I moved the part of the application that speaks to > > > mssql over to mod_python/apache and that solved the problem while we > > > were running on sql server 2000. > > > > > > I'll try to analyze this some more and get back to you.. thanks for the > > > help. > > > > > > Arnar > > > > > > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
