2007-07-16 13:34:56.59  logon Login failed for user 'JUnitCustomer'.

2007-07-16 13:34:56.67  logon Login failed for user 'JUnitCustomer'.

2007-07-16 13:34:56.71  logon Login failed for user 'JUnitCustomer'.

2007-07-16 13:34:56.84  logon Login failed for user 'JUnitCustomer'.

2007-07-16 13:35:12.43  spid4 ResType:LockOwner Stype:'OR'...

You bet... thanks for the feedback.

Would appreciate two things please... since you obviously can't get my last name correct, please call me "Jeff".

Second... I asked you to post...

Heh... I jumped the gun a bit... Oleg's code seems to do the trick nicely, though.

Heh... even better... nicely done!

Do NOT use ISQL!!!  It is severely deprecated compared to OSQL.  I'm not even sure why they left the bloody program available.  And, don't confuse ISQL with ISQLW which is...

P.S.  And, you don't need to see the KEY in this case... the report not only tells you which proc is doing it... it also tells you the line numbers...

Isolation levels may help, but the real problem is going to be in the code.  If you have explicit transactions that look like the following, you may want to consider...

4 day work week... would cut my hours from 60 to only 48

Perfect...

OK, Molly... I just gotta ask... you mean to tell me that you tried a command, that you got from somebody, on a production system without looking it up in Books Online?...

... and it will allow index SEEKs

DECLARE @MyRows INT 

SELECT TOP 1 SampleUnit_ID FROM #Sps

SET @MyRows = @@ROWCOUNT

IF @MyRows...

Heh... I don't know where they came up with the idea that SELECT INTO is slow... especially if the target DB has no triggers or keys and especially when the...

I'm thinking you need to post the SP_Generate_Inserts proc... let us see what we can do to make it less RBAR dependent...