Viewing 15 posts - 7,756 through 7,770 (of 22,226 total)
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
Deepak Burkul (7/11/2014)
yes this is interview question and i am going to learn more on execution plan of SQL server that time i get this confusion about Physhical Join...
"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:15 am
SQLRNNR (7/10/2014)
Grant Fritchey (7/10/2014)
SQLRNNR (7/10/2014)
Grant Fritchey (7/10/2014)
"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:07 am
SQLRNNR (7/10/2014)
Grant Fritchey (7/10/2014)
"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 10, 2014 at 10:54 am
Chowdary's (7/10/2014)
I think this is ok for all of us if i say like Thank you all...
But one thing whenever i post a query i get the answers...
"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 10, 2014 at 7:52 am
I get it. I'm not the brightest bulb in the box, but I can usually understand the logic of processing data most of the time. I'm utterly at a loss...
"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 10, 2014 at 7:50 am
Without the wild card on the comparison to 'R' you might as well drop the LIKE statement and say <> instead.
"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 10, 2014 at 6:45 am
This question gets asked a lot. You can search out the answers. In fact, I'd practice learning how to look up stuff on the internet. Don't assume that you 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 10, 2014 at 6:44 am
And Loops Join.
But what's the real question? Is this an interview question, or are you looking to solve a problem?
"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 10, 2014 at 4:55 am
Viewing 15 posts - 7,756 through 7,770 (of 22,226 total)