Viewing 15 posts - 18,001 through 18,015 (of 22,219 total)
Jack Corbett (3/17/2009)
GilaMonster (3/17/2009)
Bob Hovious (3/17/2009)
"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
March 17, 2009 at 8:18 am
Also remember that those estimated costs, are estimated, not actual. Execution can be quite a bit different than what is represented, and in a good 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
March 17, 2009 at 5:25 am
Sounds like you have the Resource Governor in place. I'm not that familiar with it, but I would suspect there would be some way to set this query to 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
March 16, 2009 at 7:44 pm
Well done and congratulations. Deliver on half the list and you've earned your raise for the year (and you have an agenda for next 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
March 16, 2009 at 7:37 pm
I have not personally done an upgrade in that fashion. Based on my understanding of how it works, yes, but that's from reading documentation. If you want to be absolutely...
"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
March 16, 2009 at 12:37 pm
That's a huge topic. First, you need to figure out what is causing the performance to slow down. Since, at this point, you're completely in the dark, I'd suggest taking...
"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
March 16, 2009 at 9:31 am
Jack Corbett (3/16/2009)
"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
March 16, 2009 at 8:16 am
That's a huge topic. First, you need to figure out what is causing the performance to slow down. Since, at this point, you're completely in the dark, I'd suggest taking...
"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
March 16, 2009 at 8:12 am
Do you mean in terms of licensing or in terms of physically can it be done? If the latter, yeah. You're talking Standard edition to Standard Edition. It shouldn't be...
"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
March 16, 2009 at 6:24 am
The query was resolved through auto-parameterization because it was a trivial plan. A trivial plan is not kept in cache because there is almost no generation cost for them. That'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
March 16, 2009 at 6:19 am
Is BlogEntry by chance a view? Does the underlying table have a different datatype than what you have presented here?
"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
March 16, 2009 at 6:15 am
I worked somewhere similar, everyone in the company had 'sa' privs on production. Made for a few entertaining late night phone calls followed by some serious screaming matches the next...
"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
March 16, 2009 at 6:13 am
The issue is that you have either table or column collation settings on the first set of data are different than on the second set. You'll need to look at...
"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
March 16, 2009 at 6:07 am
Only if you can't reapply them. It's fairly common practice for really large scale data moves to remove indexes and foreign keys at the beginning of the move and then...
"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
March 16, 2009 at 6:01 am
moojjoo (3/14/2009)
"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
March 14, 2009 at 10:17 am
Viewing 15 posts - 18,001 through 18,015 (of 22,219 total)