Viewing 15 posts - 16,021 through 16,035 (of 22,226 total)
Interesting stuff. The bad plan, on the higher memory machine is using less memory than the good plan on the more memory machine. I'm thinking though that the statistics on...
"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, 2009 at 1:04 pm
You can try using query hints, but the fundamental problem is the approach you're taking with the query. Ad hoc or dynamic SQL like this will create a different execution...
"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, 2009 at 5:46 am
castillo.sergio (12/17/2009)
After a lot of tests in production and test environments, the result is that when we change the amount of RAM memory...
"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, 2009 at 5:43 am
And... Same number of processors, same cost threshold for parallelism, same ANSI settings on the connections...
Just a few more things that can result in execution plans changing.
"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, 2009 at 1:10 pm
You'll also need VIEW DATABASE STATE for some of the DMV'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, 2009 at 1:08 pm
GilaMonster (12/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
December 16, 2009 at 11:48 am
The Dixie Flatline (12/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
December 16, 2009 at 11:06 am
This is more or less a paging problem. There are a number of possible solutions:
http://www.sqlservercentral.com/articles/66030/%5B/url%5D
http://www.sqlservercentral.com/scripts/31280/%5B/url%5D
These are just the first couple that I came across after searching on the site. There...
"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, 2009 at 9:37 am
Everything else is absolutely equal, identical databases, identical indexes on the databases, identical statistics on the indexes, identical queries, identical parameters... I've moved databases between servers before without the execution...
"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, 2009 at 9:33 am
The only way you can do this is if you've set up some auditing method prior to the deletes occurring or if you've got a trace running that captured 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 16, 2009 at 9:27 am
I'm sorry, I'm not there, so I can only answer based on the information you've provided.
From what you've said, a long running process was reading some large piece of data....
"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, 2009 at 9:24 am
The Dixie Flatline (12/16/2009)
I have a question about penance, Grant:Can I repent if I'm not certain I have ever pented in the first place?
You're asking 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 16, 2009 at 9:20 am
It really depends on what you're doing with SQL Server. Let's say you implement the hierarchy data type. VS 2005 won't be able to consume it. But if you keep...
"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, 2009 at 9:10 am
Then use a derived table and join against it. That would, more or less, be the equivalent of maintaining one WHERE clause and then using it for sub-selects.
"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, 2009 at 9:06 am
Compression is only available for Enterprise.
Cool stuff though.
"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, 2009 at 9:02 am
Viewing 15 posts - 16,021 through 16,035 (of 22,226 total)