I think You should use i.e. Read Commited with NoWait option in Your SELECT queries. But I wonder - if it is possible to set some property whilst connecting to Database, because changing all SELECT queries in my application will take a rather long time....Could someone help? Best regards, Marcin Pytel
Uzytkownik "Dave Arthur" <[EMAIL PROTECTED]> napisal w wiadomosci news:[EMAIL PROTECTED] > Hi, > > We are trying to replicate the way Oracle handles transaction isolation in > SAP-DB. > > Our scenario is > > - we have long transactions where large numbers of rows get loaded into > table(s). > - the consistency of these transactions across the tables is important. > - users query these tables constantly > - we want the user query to return data in the table ignoring any > transactions that may be in progress. > - we want the user query to return effectively immediately - ie not wait for > any transactions to complete or be rolled back. > > What we have observed when trying different isolation levels is that > basically the user waits until the transaction(s) is/are complete, except if > we use the READ UNCOMMITTED option - which then returns data that we don't > the user to see. > > Oracles behaviour is exactly what we want - essentially items in > transactions are hidden from users select statements. > > Does anyone know if SAP-DB can mimic this behaviour. > > > Cheers > > > Dave Arthur > Technology Partners Australia > [EMAIL PROTECTED] _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
