Viewing 15 posts - 15,226 through 15,240 (of 22,232 total)
Lynn Pettis (4/30/2010)
Grant Fritchey (4/30/2010)
Lynn Pettis (4/30/2010)
"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
April 30, 2010 at 12:46 pm
Best tool I've found for doing this is Quest's Benchmark Factory. I'm not even sure they still offer it. At one time Idera had a tool for doing this as...
"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
April 30, 2010 at 12:41 pm
Lynn Pettis (4/30/2010)
"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
April 30, 2010 at 12:39 pm
Threads are managed by SQL Server and the operating system.
What is it that you're trying to do?
"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
April 30, 2010 at 11:24 am
jcrawf02 (4/30/2010)
Right, obviously not SQL Compare. We should use Access.
You are so behind the times... Haven't you heard, Powerpivot in Excel is the new mechanism for database storage & retrieval....
"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
April 30, 2010 at 11:18 am
Lynn Pettis (4/30/2010)
"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
April 30, 2010 at 11:16 am
Cory E. (4/30/2010)
Perhaps I do not understand fully the situation, but, you can make no changes, but must add the constraint...WITH NOCHECK ?
Excellent notion. That may very well be what...
"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
April 30, 2010 at 8:35 am
Can you post the query and the execution plan, and if possible sample data & structure.
It's hard to know what the precise problem is without seeing this information. I 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
April 30, 2010 at 8:26 am
I agree with Brandie.
I will add this though, if your index was truly covering, and the one used by the execution plan, you shouldn't get a key lookup. So 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
April 30, 2010 at 8:19 am
There's little you're going to be able to do. You're selecting a sufficiently large number of rows for deletion that you need scans to retrieve them.
"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
April 30, 2010 at 8:14 am
It's difficult to be sure about execution plans and the issues when looking at estimated plans. When possible, please post actual plans.
The OR (ID IN... part of the query might,...
"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
April 30, 2010 at 8:12 am
That only occurs when a restore is run. It has to occur because after a database is restored, there is no way that SQL Server can be assured that...
"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
April 30, 2010 at 7:54 am
No, don't create more files. The issue is the code and the indexes. That is almost always the issue. You can only temporarily solve most problems by throwing more hardware...
"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
April 30, 2010 at 6:16 am
It could simply be a bitch session, but then again, a valued employee might have some valid issues that the company could address. Taking myself as an example, I'm, less...
"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
April 30, 2010 at 6:13 am
I don't think so, no. The problem is, I'm having a hard time understanding the issue. If you want unique data.... you have to make the data unique. You can't...
"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
April 30, 2010 at 6:08 am
Viewing 15 posts - 15,226 through 15,240 (of 22,232 total)