C
Chris Hough
Hi,
I was wondering if you could use SqlCommand.BeginTransaction(
IsolationLevel.ReadUncommitted ) to speed up a database read, and if so, is
it necessary to perform the EndTransaction after the read is complete? Can
you use this approach for asynchronous database reading as well?
Any suggestions are welcome - my problem is that there are several users who
are notified any time a particular table is changed, and they will all try
and read the table the moment they are notified, and noticable delays occur
(longer than you would expect from the time it takes to get the result set
from running the query from the Query Analyzer - not necessarily a fair
comparison).
Any help would be appreciated. Thanks in advance.
I was wondering if you could use SqlCommand.BeginTransaction(
IsolationLevel.ReadUncommitted ) to speed up a database read, and if so, is
it necessary to perform the EndTransaction after the read is complete? Can
you use this approach for asynchronous database reading as well?
Any suggestions are welcome - my problem is that there are several users who
are notified any time a particular table is changed, and they will all try
and read the table the moment they are notified, and noticable delays occur
(longer than you would expect from the time it takes to get the result set
from running the query from the Query Analyzer - not necessarily a fair
comparison).
Any help would be appreciated. Thanks in advance.