Viewing 15 posts - 16,951 through 16,965 (of 22,219 total)
You've got a mixed set of ANSI & non-ANSI joins (some are "tableA, tableB" and some are "TableA JOIN TableB ON"). First thing I'd do is make them all ANSI...
"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
July 21, 2009 at 11:15 am
Yeah, Lynn has it right. That's not a good thing. Not only should you do what he said, but I'd review the other eight indexes. See if there are duplications...
"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
July 21, 2009 at 11:11 am
I'm not sure if Steve can move just the question or not. Just repost it. However, what I said still applies. Wait states are what will tell you the cause...
"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
July 21, 2009 at 8:38 am
Don't just compare query times or CPU load, look at the wait states. What are processes waiting on inside the system. That will tell you where the bottleneck 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
July 21, 2009 at 8:25 am
Matt's advice is definitely good.
Here's a local article: http://www.sqlservercentral.com/articles/Administration/performancemonitoringbasiccounters/1348/%5B/url%5D
There are others. Just do a search in the box at the top of the screen.
I don't usually try to plug...
"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
July 21, 2009 at 6:57 am
You could run a query using sp_who2 to see who's connected. You can also click on the Activity Monitor icon, which will open the activity monitor and show who's connected.
You...
"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
July 21, 2009 at 6:53 am
Gail has explained, at length, many of the behaviors of COUNT(*) over at her blog[/url]. In a nutshell, SQL Server is smart enough to figure out which index, table, statistic,...
"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
July 21, 2009 at 6:47 am
Main stream support for 2000 ends in June of next year, 2010. Which, is less than a year away... Yikes!
"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
July 21, 2009 at 6:41 am
I'd suspect pretty strongly you're getting blocking. If you have a blocking script, I'd run it (if not search for one in the SSC scripts over on the left), 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
July 20, 2009 at 10:58 am
Assuming a reasonable distribution of data, I would have expected to see a seek on this...
You're only accessing a few columns on the Pupil table, you might try using...
"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
July 20, 2009 at 8:24 am
GilaMonster (7/20/2009)
I can't see anything that's forcing the scan. Makes no sense...
Whew! That makes me feel better. I'm digging through this trying to spot something. I figured you were 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
July 20, 2009 at 8:14 am
Thanks. I'm glad the book was useful. Post a review on Amazon!
😀
As to this, it does look like the statistics are up to date. I'm not sure what's happening precisely....
"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
July 20, 2009 at 8:01 am
There's only been a few posts this weekend. 4-6 at most.
"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
July 20, 2009 at 7:17 am
I can't see the .sqlplan file. Can you post it again?
It sounds like you might be seeing parameter sniffing.
"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
July 20, 2009 at 7:14 am
Yes, the Profiler gui is great for browsing already captured data, but it is a dangerous place to try to capture original data. Here's an explanation of why[/url].
"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
July 20, 2009 at 7:12 am
Viewing 15 posts - 16,951 through 16,965 (of 22,219 total)