Viewing 15 posts - 10,981 through 10,995 (of 22,226 total)
Honest answer here, if I had to do that, I'd use the command-line utility built into SQL Compare from Red Gate. It's the easiest way I know to make 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
April 27, 2012 at 12:16 pm
billo (4/27/2012)
"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
April 27, 2012 at 8:48 am
Or, for that matter, check out Jonathan Kehayias' & Ted Krueger's book. It's a free download.
"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
April 27, 2012 at 8:28 am
GilaMonster (4/27/2012)
Grant Fritchey (4/27/2012)
"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
April 27, 2012 at 8:16 am
Is is possible that the issue is not SQL Server? No blocking, low cpu, normal memory, low disk... It sure sounds like SQL Server might be OK (except 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
April 27, 2012 at 7:45 am
Deadlocks aren't going to be the problem. It's blocking that you need to look for. The process that is blocking others is likely to be the issue.
Also, look at 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
April 27, 2012 at 6:47 am
Focusing on nothin but reads, 23 is worse than 15. But as Gail says, this is a trivial difference. I'd only get worked up if this query were called hundreds...
"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
April 27, 2012 at 6:44 am
Just remember that this is only going to show the executions since the last time a given query was loaded into cache. Recompiles or aging out of cache will change...
"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
April 27, 2012 at 6:41 am
I'm not so sure I'd use a trigger. Those things are notorious performance and maintenance headaches.
What about using the OUTPUT clause. You can output the IDs generated from an INSERT...
"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
April 27, 2012 at 5:08 am
Just a different technology set. Go for it.
And, if there isn't a MySqlServerCentral, you get to go and create it. Although you might want to change the name.
"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
April 27, 2012 at 5:05 am
Data growth? Additional resource use leading to contention? Do you have memory, cpu & IO tracking over the same two time periods to compare how the whole system was behaving?
"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
April 27, 2012 at 5:02 am
There's no need for proof. It's right there in the SQL Server documentation as provided by Microsoft, the people who wrote the software.
"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
April 27, 2012 at 5:00 am
Retire? What's that word mean?
I'll be a geek til the day I die. If I'm lucky, I'll get paid for it most of the way.
"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
April 27, 2012 at 4:47 am
danaanderson (4/26/2012)
"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
April 27, 2012 at 4:38 am
20,000 rows is not that much. Even tripling it to 60,000 rows is still not much. Returning four columns doesn't mean much because I don't know the data types of...
"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
April 26, 2012 at 1:21 pm
Viewing 15 posts - 10,981 through 10,995 (of 22,226 total)