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 :) > > 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=570896&SiteID=1) seems > to point to a similar opinion, & points the finger at db connector > parameters. > > For anyone else who reads this looking for an answer to their own > issue, so you know, we have decided to make changes to our database > configuration options to remove the default locking of records during > a query, as that looks like it may resolve our particular issue. We > have the luxury of not having our data used in a way that requires > locking. This approach may not be appropriate for other users, but it > does suit our needs, so we'll try this out... > > On May 14, 11:53 am, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > 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 [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 -~----------~----~----~----~------~----~------~--~---
