Viewing 15 posts - 19,801 through 19,815 (of 22,226 total)
Usually we bump it up to 20 as a general rule.
"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
August 7, 2008 at 1:20 pm
Or, you might want to consider increasing the cost threshold for parallelism on your server. I've usually found the default is just too low, causing queries that don't need it...
"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
August 7, 2008 at 1:06 pm
Is it the log file? Maybe you're in Full Recovery mode and not running log backups?
"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
August 7, 2008 at 8:19 am
Pick up a copy of Kalen Delaney's Inside SQL Server 2005: The Storage Engine. That will give you a lot of the kind of information that you're looking for.
"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
August 7, 2008 at 6:32 am
The correlated sub-queries at the top of your select statement are going to give you coniptions as this scales. The more data it hits, the slower these will run:
...
"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
August 7, 2008 at 6:31 am
You will get slightly better performance combining the two procedures. Avoiding the recompile and the waits that it entails will help.
Honestly though, it's not a solution to your problem. You're...
"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
August 7, 2008 at 6:26 am
Log file full
Backup failed
Errors with a severity higher than 16
Those are the three most useful ones.
"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
August 7, 2008 at 6:23 am
First, and most important, before you worry about a tool, you need to focus on your process. Discipline around how and when you deploy is more important than the tool...
"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
August 7, 2008 at 6:21 am
More than a few of us on are Linked-In. It is like Gail said though, I would only recommend someone after a pretty long relationship that involves more than a...
"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
August 7, 2008 at 6:14 am
You may need to post your code because that should work fine. As one of the previous posts said, you may have your PK improperly defined.
"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
August 7, 2008 at 6:10 am
It sure makes the editorial I just read in SQL Server Magazine sound a little weird. He mentions the release "later this year" of 2008. I thought it sounded strange...
"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
August 7, 2008 at 5:32 am
Thanks for all the responses.
I got one yesterday, I think it was maybe the third one I've received over the years (I'm hardly one of the "go-to" guys). It was...
"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
August 7, 2008 at 5:27 am
Cool. Thanks for sharing.
"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
August 6, 2008 at 1:32 pm
Everything the other guys said is 100% accurate, but one other note, you may want to take into account.... With really simple queries like the ones you showed, the optimizer...
"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
August 6, 2008 at 11:06 am
I agree with GSquared. Both enabled, everywhere. Also a script that checks indexes and then does a rebuild or reindex based on fragmentation. Also, there is the occasional index 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
August 6, 2008 at 11:02 am
Viewing 15 posts - 19,801 through 19,815 (of 22,226 total)