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 cant locate the string "FMTONLY" within the MSSQL dialect at all. So this is not something SQLA is issuing. > > I would like to explicitly make this a NOLOCK select, to prevent these > queries from generating locks, as these locks appear to be impacting > our application performance & server stability. Can anyone point me in > the direction of where such a change could be made? our MSSQL devs might be able to help here but also you might want to see what the source of the locking is (i.e. some (Py)ODBC thing); SQLA is not issuing any locking. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
