Viewing 15 posts - 16,006 through 16,020 (of 22,219 total)
The order in which you place these things and whether or not you place the criteria in the ON or WHERE cluase (at least for INNER JOINS) does not matter....
"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 18, 2009 at 8:16 am
I'm not sure if it's a skill, although it must partly be.
One old story. I wrote an app for managing user access to a database and turned it over 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 18, 2009 at 8:11 am
There are a number of ways you can do this, but in general, I'd take what you're doing with trace events (and I'd only capture rpc complete and sql batch...
"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 18, 2009 at 7:50 am
What data type is date_out? Can you post some sample data from it?
BTW, running that function on your column in the WHERE clause will prevent indexes from being used.
"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 18, 2009 at 7:37 am
I'm running the 2008 R2 Enterprise on a netbook in Win 7 with 1gb of RAM. It won't win any speed contests, but it functions, barely. Yes, you can do...
"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 18, 2009 at 7:34 am
Unless you're in a situation where your database is consistently too small and the auto-grow is set too low, space is seldom the cause of performance issues.
You said you looked...
"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 18, 2009 at 7:31 am
All stats for a table were necessary at one time or another or they wouldn't be there. It is possible though that system generated statistics on columns without indexes may...
"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 18, 2009 at 7:28 am
Glad that it worked out.
"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 18, 2009 at 6:31 am
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
Viewing 15 posts - 16,006 through 16,020 (of 22,219 total)