Viewing 15 posts - 12,316 through 12,330 (of 22,224 total)
Gail & Gus have largely addressed everything. Only thing I'll add is if you want details on configuring tempdb go by Paul Randal's blog sqlskills.com. He has several excellent articles...
"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 14, 2011 at 7:04 am
The load on tempdb absolutely increases. You have to be sure that you have that configured correctly and that you can support more space in tempdb. Other than that, 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
June 14, 2011 at 6:09 am
Sorry, I didn't see this question (still can't get the RSS feed to work for this topic). I've been doing lots of experimentation with SQL Azure, as Steve pointed out....
"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 14, 2011 at 5:59 am
For really small sets of data, no, you won't see much of an improvement. But as you start stuffing more keys on a page for an index, you will see...
"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 14, 2011 at 5:11 am
Alphabetically 'S' is greater than 'C'
If you think you're comparing the lengths of the strings, you're not. You need to use LEN to see the number of characters or DATALENGTH...
"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 14, 2011 at 5:01 am
There are places where you will run into situations where the 2000 query can run faster than the 2005 query. In all the cases I've seen so far, there were...
"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 14, 2011 at 4:57 am
Compression gives a huge performance bonus at a slight cost to CPU. Yes, you're moving less to & from the disk, but even more importantly, you're storing more rows on...
"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 14, 2011 at 4:52 am
The real question is, why are you so concerned with ghost record cleanup? In certain situations where you have extremely high volume deletes you can run into issues, but in...
"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 14, 2011 at 4:46 am
Instead of using group by, try using TOP 1 and an ORDER BY statement. That usually works better.
"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 14, 2011 at 4:42 am
I'd start with this excellent article from Buck Woody. He lays out most of what you need to get going.
"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 14, 2011 at 4:41 am
Look up sp_changedbowner in the Books Online. That will let you change the database owner to another login and then you can drop hers. I would recommend dropping her login...
"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 14, 2011 at 4:25 am
As long as the login isn't mapped to users that own objects or databases, sure you can drop it. But I would check the ownership very carefully before you drop...
"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 13, 2011 at 7:39 pm
And with all that, now it's going to be even harder trying to figure out why you're getting performance differences and where those differences are coming from. I hope 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
June 13, 2011 at 6:11 pm
61 different statements... You're on your own.
I will note that statement 7 & 8 (two of the highest, one in ON & one in OFF) both show ANSI_WARNINGS set to...
"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 13, 2011 at 5:08 pm
todinhkhoi (6/13/2011)
Thank you for the instructions. I followed them, and finally I was successful in retrieving the data I wanted. I have another 2 questions...
"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 13, 2011 at 5:00 pm
Viewing 15 posts - 12,316 through 12,330 (of 22,224 total)