Viewing 15 posts - 19,036 through 19,050 (of 22,219 total)
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
Only if you're assuming that the entire set of lookup values is replaced each year. If the assumption is that the lookup value consists of the value and the year...
"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 12:58 pm
You'll probably need three inserts, but you can insert into each of the parent tables, get the ID's generated and then insert into the third table based on those ID's...
"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 10:39 am
iqtedar (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 10:37 am
Sure, you can use the OUTPUT clause of the INSERT query. This will allow you to capture ID's created during the INSERT and you can then pass them on 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 16, 2008 at 9:30 am
Tune the query is the first thing that comes to mind. Make sure you've got the right indexes in place on the tables and that the query is using them...
"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 9:03 am
GilaMonster (12/16/2008)
Grant Fritchey (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:49 am
You can load the file into a database and then run queries against it. That's how I've been doing it for years. That way you can get aggregates and see...
"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:44 am
Viewing 15 posts - 19,036 through 19,050 (of 22,219 total)