From: Alexander P. <ale...@gm...> - 2011-02-10 18:51:39
|
On 10.02.2011 21:08, unordained wrote: > I've got another team trying to access my firebird database from sqlserver, using > 'openquery' (they're pulling from themselves, me, and another access database, and that > seemed like the cleanest solution at the time.) > > Their queries are purely read-only queries. > > At the moment, my database is mostly locked up because of a migration script running; > almost all records are being touched by a very long-running process. > > It seems in the ODBC configuration GUI that their only options result in either: > a) something like read-committed + no-rec-version + nowait, which blows up with > deadlock errors (because it's told not to wait on the new record versions, which won't > be available possibly for days) > b) something like read-committed + no-rec-version + wait, which just hangs forever > (because my code's not going to commit for days.) > > Neither of those is good. > > I'm not sure what transaction settings they're using in sqlserver, and I haven't found > any documentation about how sqlserver configures openquery (based on the sqlserver > transaction settings?), and how that passes through to the ODBC layer -- but is there > any way I can get them to use the transaction mode I want, which is just a plain read- > committed, rec-version (wait won't matter), or what I always use, snapshot isolation? I > don't see anywhere to configure exactly that in the ODBC GUI, and what we change there > *seems* to have an effect, so regardless of sqlserver/openquery, what we configure > matters -- but I can't configure what I want. Is there a registry setting, a text file, > some other place you can configure stuff like this? > > Hi, ODBC driver 2.0 RC2 uses read-committed/rec-version by default (versions before RC2 used read-committed/no_rec-version). Read/Write and Wait/NoWait are configured in ODBC configuration GUI. Regards, Alexander -- Alexander Potapchenko Lead developer LASP technology, http://www.lasptech.ru |