Viewing 15 posts - 7,741 through 7,755 (of 22,219 total)
Deadlocks are fundamentally a performance problem. What's the situation with the server? How are the waits and queues? Are you running out of memory, I/O, or CPU? You may need...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 9:00 am
GilaMonster (7/11/2014)
Grant Fritchey (7/11/2014)
You would want the fixed length columns stored first and then any variable length columns.
Not really, because SQL stores the columns on the page that way no...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 8:55 am
If you were down to trying squeeze the last microsecond of performance by increasing the efficiency of performance, yes, this would matter. You would want the fixed length columns stored...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 8:39 am
Take a look at the book in my signature line. Get the 2012 version. It's still applicable to 2008 and it fixes some errors.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 7:00 am
You have to restart. There's no way to recover in place once the chain is broken.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 6:59 am
Generally you need to have the latest version of SSMS to access the latest version of SQL Server. You can access earlier versions from the latest one, but I've always...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 6:23 am
But she's talking about variables within the query, not parameters. Parameters are sampled by default, variables can only be sampled during a recompile situation. The other issue is, if your...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 6:08 am
Cody K (7/11/2014)
Grant Fritchey (7/11/2014)
That's probably the cause of the deadlock.Isn't the cause something between the Sch-S and Sch-M locks? How does an update factor into that?
I'm just referencing the...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 4:24 am
The two queries seem to be taking out locks in different orders. On a guess, you have some type of SELECT statement that's part of the procedure UpdatePurchaseOrderWorkQueueStatus that...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 3:53 am
It sounds like either the disk is full, or you have a transaction that's so big that it's going to fill the disk and/or the filegroup.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 3:49 am
Please don't cross post, it just confuses the discussion. All answers to this link
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 3:49 am
Check your code. Are you using a function on a column or something along those lines. That might prevent the existing index from being used.
More likely it's suggesting something with...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 3:45 am
If the index isn't needed by the data load process, yeah, I'd drop and recreate it. But verify that it's not needed first.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 3:43 am
For the most part updating statistics runs in a similar fashion to any other query in the system. The degree of parallelism is set at the system level and SQL...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 3:41 am
You'll only see output for the things that return an output from your statements.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 11, 2014 at 3:31 am
Viewing 15 posts - 7,741 through 7,755 (of 22,219 total)