Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Isolation level using linked server Expand / Collapse
Author
Message
Posted Thursday, November 22, 2012 11:54 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 17, 2014 5:09 AM
Points: 156, Visits: 661
Our situation:
- our EPR system uses Progress database (blackbox for me, don't even know where it is installed)
- on a Windows Server 2003 instance we have a ODBC datasource (System DSN), which uses OpenEdge 10.1C driver and is connected to the Progress database. The driver's isolation level is 'read uncommitted'
- on the same Windows system there is a SQL server 2005 installed and if I run 'dbcc useroptions' in one of the database, the isolation level is set to 'read committed' (althoug I doubt that this has any relevance in my example)
- on the SQL Server 2005 we have a linked server to the Progress database, which uses the ODBC data source
- we query Progress database via the openquery command, simplified:
select Country
from openquery(LINKED_SERVER_NAME, '
select distinct Country
from XXX.Countries
where Id = 10
') x

The problem is, that sometimes the query throws
Cannot fetch a row from OLE DB provider "MSDASQL" for linked server "LINKED_SERVER_NAME"

exception. As I profiled the execution of the query, I saw that the exception is thrown by the OpenEdge driver:
OLE DB provider "MSDASQL" for linked server "LINKED_SERVER_NAME" returned message "[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Failure getting table lock on table XXX.Countries"

So it seems, that the query tries to lock the XXX.Countries, although the OpenEdge driver is set to 'read uncommitted'. Why is this happening?

I will try to play with various settings (isolation level on database level, set transaction isolation level in each transaction, ...) and do a thorough profile for each query, but this will be time consuming and also - the exceptions is thrown randomly so it is hard to profile. Any additional informations about this topic would be much appreciated.
Post #1388056
Posted Monday, November 26, 2012 2:11 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 3:36 AM
Points: 6,131, Visits: 7,171
I'm not sure we can help you with this. Openedge seems like a proprietary driver, and Progress appears to be a Teradata solution. The problem sounds like it's in the ODBC connection directly, or there may be settings on the foreign server that's overriding your isolation, but really, not many of us are experts in that database system.

Hopefully someone can come by and prove me incorrect but your best bet would probably be to get on a forum board dedicated to Progress, Teradata, or Openedge. I just didn't want to leave you hanging like you were being ignored though. I just think noone here really knows.



- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
Post #1388843
Posted Tuesday, November 27, 2012 1:26 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 17, 2014 5:09 AM
Points: 156, Visits: 661
Thanks for reply, willl try to find some ProgressDB forum and ask there.
Post #1389008
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse