Viewing 15 posts - 10,846 through 10,860 (of 22,226 total)
You need a much more thorough collection of data in order to determine the causes of the high cpu. Yeah, it could be SQL Server, but from what you've said...
"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
May 31, 2012 at 4:27 am
Alex-668179 (5/31/2012)
Fine, but should it then also always be the (preferably meaningless?) primary key? Or an index that is more likely...
"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
May 31, 2012 at 3:41 am
jasona.work (5/30/2012)
How do you feel about the SQL in the City[/url] events?
I took a look at the agenda for 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
May 30, 2012 at 8:29 am
anthony.green (5/30/2012)
"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
May 30, 2012 at 4:26 am
Mark Fitzgerald-331224 (5/29/2012)
"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
May 29, 2012 at 6:12 am
anthony.green (5/28/2012)
I know Safari has its limitations, so I use the MobiSSRS (free version) app instead of Safari which works...
"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
May 29, 2012 at 5:52 am
Disparity between estimated & actual points towards either bad statistics on the data, or good statistics, but the data is skewed which is causing bad parameter sniffing for some values....
"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
May 29, 2012 at 5:13 am
Jeff Moden (5/27/2012)
Revenant (5/26/2012)
Steve Jones - SSC Editor (5/25/2012)
Jeff Moden (5/25/2012)
Brandie Tarvin (5/25/2012)
"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
May 29, 2012 at 4:27 am
When you're defining a join, you should define the columns that join the two tables together. So that you're ON condition is something along the lines of
A.ID = B.ID
If...
"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
May 25, 2012 at 8:10 am
Gianluca Sartori (5/25/2012)
paul.knibbs (5/25/2012)
"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
May 25, 2012 at 5:52 am
If you can post the execution plans, I would be guessing less, but, guessing, I'd say that it's probably a parameter sniffing issue. Take a look at the estimated values...
"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
May 25, 2012 at 5:03 am
This is a classic issue for backups and one that leads to severe problems when you try to recover these backups. I detail this issue, along with a few others,...
"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
May 25, 2012 at 4:55 am
It's certainly possible that's the cause, but I'd be more concerned that the query is identical between both databases and, more importantly, that the statistics are updated in exactly 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
May 25, 2012 at 4:51 am
Are we talking connections or transactions? If you have 4000 open & uncommitted transactions, yeah, I'd be having screaming fits right about now. That's locks being held open, possibly leading...
"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
May 25, 2012 at 4:47 am
The reads measures are based on pages, yes.
As for time, it really depends on where you're getting the measure and what you're looking at. If, for example, you're looking 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
May 25, 2012 at 4:45 am
Viewing 15 posts - 10,846 through 10,860 (of 22,226 total)