Viewing 15 posts - 13,471 through 13,485 (of 22,219 total)
GilaMonster (1/26/2011)
I'm just not seeing a future here at the moment. The IT industry is...
"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
January 26, 2011 at 4:52 pm
Jeff Moden (1/26/2011)
Grant Fritchey (1/25/2011)
"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
January 26, 2011 at 4:48 pm
Just know that if you've rebooted the machine or restarted the SQL Server instance, all information is lost from the index usage DMV. There's absolutely no guarantee that will show...
"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
January 26, 2011 at 4:40 pm
It kind of depends on what the data is. If it's an address, '1313 Mockingbird Lane,' I wouldn't sweat it (although, you can, I've seen systems that normalize street numbers)....
"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
January 26, 2011 at 12:49 pm
Take a look at the execution plan. On a guess, it's doing scans based on some foreign keys, loading that data into cache in the first query, just reading from...
"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
January 26, 2011 at 12:46 pm
Just speaking in theory, because without code & structures, it's hard to know what you're going for, you can combine two different result sets using the UNION or UNION ALL...
"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
January 26, 2011 at 12:45 pm
You can't base performance measurement off of execution plans. The only way to absolutely know which statement in a batch took longer is to have measurements, using extended events or...
"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
January 26, 2011 at 12:39 pm
If it was running good until Sunday, what changed on Sunday? New code release, service pack, new client, new users? Something had to have happened to it.
"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
January 26, 2011 at 12:14 pm
Gail, congrats on getting a spot on the new 24 Hours of PASS.
"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
January 26, 2011 at 9:28 am
To calculate usage over time, you'd need to gather metrics over time. You can use Permon to do this.
I can also suggest (full disclaimer, I work there) Red Gate's 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
January 26, 2011 at 9:26 am
I had a UDF I used to use as well. With smaller data sets it works fine. But if you start to grow them, I really suggest using the tally...
"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
January 26, 2011 at 9:22 am
What happened to the available bit in Table c?
The thing is, unless you're maintain a history of availability so that all entries to Table B are inserts (in which case...
"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
January 26, 2011 at 8:48 am
Take a look at this article by Jeff Moden[/url]. He shows how to use a tally table to solve the problem you're describing. It's a very efficient approach.
"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
January 26, 2011 at 8:40 am
I agree. I can't see why you would need to join to that table unless there are other fields and functions you're not showing.
"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
January 26, 2011 at 8:34 am
You should be able to, yes. Why 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
January 26, 2011 at 7:50 am
Viewing 15 posts - 13,471 through 13,485 (of 22,219 total)