Viewing 15 posts - 12,226 through 12,240 (of 22,219 total)
Gianluca Sartori (6/28/2011)
Yeah! 3000 points for me!It's a small step for most of you, it's a great step for me.
Well done. Thanks for all your 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
June 28, 2011 at 6:24 am
oluwaseunadenaike (6/28/2011)
I guess SQL profiler and the DB tuning advisor are my best bets .... what types of common performance bottlenecks should i look out 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
June 28, 2011 at 5:13 am
Pretty much everything. Did you get no turnover from the previous DBA or your manager? If not, you're in a tough spot.
Backups and disaster recovery should be your primary concerns....
"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
June 28, 2011 at 4:29 am
You need to go into SCOM itself and look at how it's collecting data from that server. From the sounds of things you have it configured to only pull data...
"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
June 28, 2011 at 4:25 am
yasubmj (6/27/2011)
Thanks Grant, i see the point. Any suggestions as to how i can solve this?
Filter the data in some fashion is the best answer I have. Assuming the selectivity...
"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
June 28, 2011 at 4:19 am
Ninja's_RGR'us (6/27/2011)
Grant Fritchey (6/27/2011)
"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
June 27, 2011 at 5:33 am
It really depends on the volatility of the data, the structure of the indexes, and the types of queries run against it. We updated statistics on an insurance system I...
"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
June 27, 2011 at 5:12 am
You're retrieving 261000 rows out of a table that has 268000 unique values (not sure if that's how many rows it has or not). I'm a little surprised that it'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
June 27, 2011 at 5:07 am
Many of the maintenance tasks you're doing can be logged operations. That would explain the increased log backup size.
Why, oh why are you shrinking the database? That is, in 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
June 27, 2011 at 4:54 am
Recovery means it is checking its integrity and rolling back/forward transactions that were open when it was shut down. There's no way to know for sure how long it 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
June 27, 2011 at 4:52 am
pcarroll-626929 (6/24/2011)
- The task manager like graphs at the top of summary values 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
June 25, 2011 at 4:42 am
This article is for 2005[/url] but it's all applicable to 2008. There are just a few new things you can do in 2008 like compression.
"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
June 24, 2011 at 6:24 am
Moving it to 2008 updated the statistics. Try doing that on your 2000 server and see how that affects the 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
June 24, 2011 at 6:21 am
If you do a little searching around in the Visual Studio documentation, there is a database and set of code specifically designed to use SQL Server for caching data between...
"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
June 24, 2011 at 6:11 am
You can install both on the same server and they'll operate just fine.
But, that's not saying that they won't impact each other. You will see contention for resources.
"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
June 23, 2011 at 9:03 am
Viewing 15 posts - 12,226 through 12,240 (of 22,219 total)