Viewing 15 posts - 17,656 through 17,670 (of 22,219 total)
Oh yeah. A few details may change, but the basic approach & scope is the same for 2008.
"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 21, 2009 at 9:00 am
Try this one
http://www.red-gate.com/specials/Grant.htm
I'm not sure it's still valid. Maybe the real book & Kindle are all that's available now.
"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 21, 2009 at 8:58 am
It sure sounds like blocking, but since you say it's not, I'd step back a bit, not look at that procedure directly and instead examine the waits and queues 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
April 21, 2009 at 8:48 am
GilaMonster (4/21/2009)
mithun.gite (4/21/2009)
GilaMonster (4/21/2009)
mithun.gite (4/21/2009)
Can any one give me a link for Query Optimization, using that i can start optimizing my queries?
I can suggest some books.
Inside SQL Server 2005: Query...
"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 21, 2009 at 8:45 am
I would have to see the code to fully understand the issue. However, no, there's no way to selectively limit the query defined within a view. The query is going...
"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 21, 2009 at 8:41 am
That's tough.
Without rearchitecting... I'd suggest setting up server side traces and capture query performance behavior. Then, go after the top poor performers. I'd focus on establishing a good set 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 21, 2009 at 8:32 am
You basically need a baseline to compare against. I'd suggest collecting the information when there are very few users on the system and then when there are lots of users....
"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 21, 2009 at 8:29 am
The one thing no one seems to have mentioned is the selectivity of the data. Just because there are 10 columns and just because each of the 10 is 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
April 21, 2009 at 8:18 am
I wouldn't recommend using this method in the WHERE or JOIN clauses of your queries, but for the SELECT list, instead of CASE statements, try this:
SELECT COALESCE(MyColumn,'') AS MyColumn
...
That will...
"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 21, 2009 at 6:24 am
You can also run it from Profier (Tools - Database Engine tuning Advisor) or from a SSMS query window (Query - Analyze Query in Database Enging Tuning Advisor).
"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 20, 2009 at 11:49 am
I agree with GSquared. Capture the query info and make decisions from there. The one other thing that you might concern yourself with is the volatility of the data in...
"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 20, 2009 at 11:45 am
GilaMonster (4/20/2009)
Jack Corbett (4/20/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
April 20, 2009 at 11:00 am
Jack Corbett (4/20/2009)
Bob Hovious (4/20/2009)
Although I have no preference, aren't they using VB with SSIS?
In 2005 yes, but in 2008 you can use C# as well. My current work...
"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 20, 2009 at 7:11 am
SQL Server is heavily involved on managing parallelism. It has to to merge the data from the various streams so, it does quite a lot of work.
"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 20, 2009 at 7:03 am
Krishna Potlakayala (4/18/2009)
fayilt (4/18/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
April 20, 2009 at 6:34 am
Viewing 15 posts - 17,656 through 17,670 (of 22,219 total)