Greg - just be careful - that has SQL injection written all over it.

From BOL:

READUNCOMMITTED

Specifies that dirty reads are allowed. No shared locks are issued to prevent other transactions from modifying data read by the current transaction, and exclusive locks set by...

As far as I know - option 1 is not "legal". You should get something squeeking at you for putting the BEGIN tran outside of the TRY, and the...

All I can say it - boy am I happy they're getting rid of that flag!

No matter how you look at it - the non-ANSI setting isn't consistent....

CirquedeSQLeil (2/21/2010)

---

Lynn Pettis (2/21/2010)

---

Or maybe...

Paul White (2/21/2010)

---

ChrisM@home (2/21/2010)

---

Blimey, what was I thinking? :blush: Of course it works like this, it would be inconsistent for it to work any other way. I guess I got...

Sorry - just remembered how Michael Coles did it.

LIKE unfortunately can returning an UNKNOWN:

set ansi_nulls off

if null like null

print 'true 3'

if not (null like null)

print 'true 3a'

if '' not like...

Paul White (2/20/2010)

---

Matt Miller (#4) (2/15/2010)

---

NULL is not a value, so as such, NULL is neither equal nor not equal to any value. Unfortunately, that also means that it's...

John Paul -

SQL Server allows you to use joins in your DELETE statements, so perhaps having EXISTS is not necessary.

Assuming the primary key in both tables is Pkey, you...

GT-897544 (2/20/2010)

---

ziangij (2/19/2010)

---

thanks...

i just checked it out.. without indexes, update query takes 30 sec.

with the indexes in places, it takes 2 min !

RBarryYoung (2/17/2010)

---

I think that it depends on a...

nadabadan (2/18/2010)

---

Matt Miller (#4) (2/15/2010)

---

The joys of null!

NULL is not a value, so as such, NULL is neither equal nor not equal to any value. Unfortunately, that also means...

ChrisM@home (2/20/2010)

---

'Course it does, it's got a CROSS APPLY in it!:hehe:

CROSS APPLY is an awesome operator to use...

Yes you will. Even in a simple recovery model every change gets logged first before the change is applied, so if your log file has insufficient space and cannot...

if you don't have access to sys.tables, then it's not a SQL Server (at least not a 2005 or 2008 server). What's the other side?

This is still going to give you trouble:

And (tEx.EventResults LIKE %)

needs to be

And (tEx.EventResults LIKE '%')

at very least