Whoops,
I wrote:
> I have a method that explicitly opens a connection and begins a
> transaction on SQL Server 2000. I use the System.Data.SqlClient.
>
> Before commiting (or rollbacking) this transaction I need to open
> another connection to use with a datareader. What is important to note
> is that I'm not interested in uncommited data. I would like to perform
> some queries on data that existed before the BeginTransaction
> instruction.
This is hardly doable because the update/insert transaction will
lock the tablerows affected for readers, if you do not specify table
lock hints in your update/insert query in the transaction.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Which is of course wrong, I ment "if you do not specify table
lock hints in your SELECT query executed during the transaction". Table
lock hints for reading uncommitted data or not locking rows for readers
are not allowed in update/insert/delete statements
FB
