Viewing 15 posts - 55,801 through 55,815 (of 59,098 total)
Heh... Not having nearly the bad day that you will if you keep trying unverified commands on your database (production or not)
That's...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2007 at 8:30 am
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'...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2007 at 7:29 am
You bet... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2007 at 7:24 am
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2007 at 6:05 am
Heh... I jumped the gun a bit... Oleg's code seems to do the trick nicely, though.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2007 at 5:59 am
Heh... even better... nicely done!
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2007 at 5:57 am
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2007 at 4:43 am
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2007 at 4:39 am
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2007 at 4:37 am
4 day work week... would cut my hours from 60 to only 48 ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2007 at 7:06 pm
Perfect...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2007 at 6:22 pm
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?...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2007 at 6:16 pm
... and it will allow index SEEKs ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2007 at 5:57 pm
DECLARE @MyRows INT
SELECT TOP 1 SampleUnit_ID FROM #Sps
SET @MyRows = @@ROWCOUNT
IF @MyRows...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2007 at 5:52 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2007 at 5:43 pm
Viewing 15 posts - 55,801 through 55,815 (of 59,098 total)