Viewing 15 posts - 12,241 through 12,255 (of 22,227 total)
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
Is the table a part of a join? Is it the bottom part of a Loop join perhaps? How many executions are there? Does that equal the number of rows?
"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 7:27 am
Where'd you get the pictures of my yard?
"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 22, 2011 at 12:53 pm
Nope.
That text column is going to be a limiter for 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
June 22, 2011 at 7:38 am
ROLLBACK is used when you have an open transaction to undo the changes for that transaction. It doesn't work after transactions have already been committed. This article [/url]I wrote 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
June 22, 2011 at 4:57 am
No, you could go one more level deep. Have three tables. One for the measure, one for the measure type (height, width, weight), and one for the business measure type...
"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 21, 2011 at 2:19 pm
No, I would have gone a different way. A heigh table, a width table, etc., and then a Type table that can be mapped to each of the other tables...
"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 21, 2011 at 11:58 am
Compusol (6/21/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 21, 2011 at 11:21 am
Viewing 15 posts - 12,241 through 12,255 (of 22,227 total)