Viewing 15 posts - 19,036 through 19,050 (of 22,226 total)
Ah sorry, different issue, different post. My mistake.
BTW, it's always helpful, but hardly necessary, that if you answer a question you posted, go ahead and post the answer. It'll not...
"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
December 17, 2008 at 6:43 am
I don't have the answer, but you might want to post the question over in the 2008 forum. If people aren't monitoring both, they may not see this.
"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
December 17, 2008 at 6:37 am
Also, if this question is related to this post:
http://www.sqlservercentral.com/Forums/Topic621088-145-1.aspx
You really shouldn't post multiple times because it just diffuses the conversation, making it harder for people to help and duplicating effort.
"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
December 17, 2008 at 6:22 am
Simply updating 46 columns should not cause a deadlock. This would cause blocking, as one resource would have to wait on another while it's update completed. You have other processes...
"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
December 17, 2008 at 6:21 am
Are these queries part of a bigger set of commands? Nothing there indicates why you'd receive a deadlock. You need to look at the statements prior to these two to...
"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
December 17, 2008 at 6:18 am
Or edit the post... that works too.
"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
December 17, 2008 at 6:14 am
Most of it is not displaying. You should try zipping it up and posting it as an attachment.
"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
December 17, 2008 at 6:13 am
To add to what Gail says, I'd also suggest, that when you're not troubleshooting deadlocks, capturing the Start command is unnecessary. Usually getting RPCComplete and SQLBatchComplete covers just about everything...
"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
December 17, 2008 at 6:12 am
You can use the OR construct or even COALESCE
WHERE SomeValue = COALESCE(@Param,SomeValue)
But the OR constract and the COALESCE construct aren't going to perform terribly well because either one will cause...
"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
December 17, 2008 at 6:03 am
How are the slots defined? Is each one an hour? You can simply write a query that uses a parameter for the particular meeting hall and a parameter for 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
December 17, 2008 at 5:56 am
Couldn't help myself. I did a google search on the OP's name. He's an Access guy and, to his credit, has posted helpful answers to others in the forums where...
"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
December 17, 2008 at 5:43 am
MGS (12/16/2008)
"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
December 16, 2008 at 8:27 pm
Usually I capture procedure calls using trace events and then you know which procedures on which databases are running long or using more cpu.
With 2005 & 2008, you can also...
"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
December 16, 2008 at 8:21 pm
But not deletion when the keys are in use, right?
"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
December 16, 2008 at 1:27 pm
Today you just want to find out which procs are hitting. Tomorrow you're going to realize that you can begin to run aggregates and groupings to put out more meaningful...
"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
December 16, 2008 at 1:02 pm
Viewing 15 posts - 19,036 through 19,050 (of 22,226 total)