READ COMMITTED is the default Isolation Level in SQL Server. This is why a select will not finish until any exclusive locks are released.

For example in my example, if...

Gabor,

I actually misread your original post. In order to insure that the second user sees the data prior to the delete while the delete is on-going you need to...

mike (6/11/2008)

---

I like to use CLR SPs when I have some special code I don't want the whole world to see. Could probably be reversed engineered but at least...

don_goodman (6/11/2008)

---

Why? You have C2 security enablement that does all the work for you to generate traces of everything. You have :fn_trace_gettable to read the traces so you don't have...

You should note...

At...

RBarryYoung is correct in each of his posts. You do need to understand the differences between Snapshot Isolation and Read Ucommitted (nolock) and BOL is the best place to...

Grant Fritchey (6/11/2008)

---

Excellent article TJ. Congratulations on a well ordered process.

Any chance of posting the code for the procs that start the traces? I'm curious about some of the details...

What are you getting for an error?

Did you ever find the answer to this problem? I was going to post the same link that Matt did. The answer is definitely there.

Duplicate post please post answers here, http://www.sqlservercentral.com/Forums/Topic514867-149-1.aspx

Duplicate post, please give answers here, http://www.sqlservercentral.com/Forums/Topic514867-149-1.aspx

Please post in only 1 forum. Posting in multiple forums just makes people post duplicate answers and does not allow for us to...

Uncle Boris,

I too have struggled to find things in Profiler in 2005. I really don't like the changes MS introduced to the interface, they made it much harder to...

Gabor,

If you change the isolation level, you do realize that user 2 is going to see the deleted records? You can also manage the isolation level at the query...

SSIS should definitely be able to move you from SQL 2000 to 2005, in fact you should be able to do a backup of the SQL 2000 database and restore...