Viewing 15 posts - 17,791 through 17,805 (of 22,214 total)
It is possible that checking the queries and getting a good index in place may help as well. I'm personally not a fan of the DTA, but it can help....
April 6, 2009 at 6:59 pm
First, turn off 1204 when you're collecting the info with 1222. It'll cut down on the noise and make it a bit easier to read.
Second. You're getting lock escalation as...
April 6, 2009 at 6:36 pm
All three queries are going after sgDataOPERATIONS. Is there a read statement prior to the delete statements that would cause lock escalation? What do the execution plans look like on...
April 6, 2009 at 1:31 pm
1204 puts out a hard to use deadlock graph. If you can, can you recapture it using traceflag 1222? That one is much cleaner and easier to read.
April 6, 2009 at 1:20 pm
Check the actual execution plan. In the properties of the various processes it will show you if you're using parallelism and how many threads were used by the process.
April 6, 2009 at 1:00 pm
Excellent. Glad you tracked it down. Thanks for posting the solution here.
April 6, 2009 at 11:33 am
I'm really against a black list. I'm far too likely to end up on it one day. Plust I'm probably not going to consult it until I've already stepped into...
April 6, 2009 at 11:32 am
Wilfred van Dijk (4/6/2009)
Yes, I know the meaning of this error, but why is the same statement giving this error in a Job and not in a query window???
Assuming the...
April 6, 2009 at 8:31 am
There's no 100% sure way to verify that things are not used in your database. As others have outlined, it's possible to see whether or not things have been accessed...
April 6, 2009 at 7:29 am
Something is holding a lock on your system. It could be a long running process or an uncommitted or unrolledback transaction. Try looking at sys.dm_os_waiting_tasks or sys.dm_tran_locks to see what's...
April 6, 2009 at 7:22 am
Don't use auto shrink. That's a major performance hit in most circumstances. If you've had some kind of over-sized transaction or error with the log backups or something that caused...
April 6, 2009 at 7:13 am
That warning is pretty straight forward. Somewhere in the code a string is getting placed that's just too long.
Also, on a side note, instead of using @@IDENTITY, I'd suggest you...
April 6, 2009 at 7:09 am
San (4/6/2009)
Somehow I managed to install SQL2k5 with different instance name and logged using "machineName\instanceName". Now another problem is that, when I select " " option in SERVER NAME...
April 6, 2009 at 7:03 am
I liked the podcast even more than the editorial.
I don't think you were only pointing at those asking questions when you suggested we needed to treat others as we...
April 6, 2009 at 6:49 am
Viewing 15 posts - 17,791 through 17,805 (of 22,214 total)