Viewing 15 posts - 15,646 through 15,660 (of 22,219 total)
Looking at it, you're getting almost nothing but clustered index scans. That means it's reading every single row on the table. Things in the queries that are causing this include:
CellGroupName...
"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
March 25, 2010 at 7:06 am
ekknaveen (3/24/2010)
I need the help to solve the below mentioned questiones.
1. <>. > =. LIKE what is the order as per performance
2. select * from tab1 where lower(name)='name' is fast...
"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
March 25, 2010 at 6:52 am
It sounds like a classic design error on normalization. Yes, given the opportunity, I'd suggest redesigning the structure and migrating the data. It won't be that hard and you should...
"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
March 25, 2010 at 6:46 am
The uniquifier (or uniqueifier) is a 4byte integer value. So from that you can estimate the cost to the size of the index. So that not only increases the size...
"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
March 25, 2010 at 6:34 am
virgilrucsandescu (3/24/2010)
And the last chapter (the checklist) should be on the desk...
"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
March 25, 2010 at 6:05 am
I agree with Gus and I'll add that I still learn more when I answer a question wrong and it gets fixed by one of the SQL-Monsters that run around...
"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
March 24, 2010 at 12:35 pm
Steve Jones - Editor (3/24/2010)
...many of the more vocal people on the East Coast...
Now who the heck are you talking about?
"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
March 24, 2010 at 10:29 am
If you're seeking to break it up in that way, then instead of ID & foreign key, maybe breaking it up by date makes more sense.
"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
March 24, 2010 at 6:20 am
I'll try to attend the Summit regardless of where it's held. That said, I'd still like to see it move around a bit. Seattle is a pretty major travel commitment...
"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
March 24, 2010 at 6:17 am
GilaMonster (3/23/2010)
Been fiddling with this on and off for a couple years now. Initial idea was just the light from...
"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
March 24, 2010 at 5:50 am
Good to have you back Barry!
"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
March 24, 2010 at 1:14 am
Nice high level of paranoia. Good job.
"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
March 23, 2010 at 5:04 am
Lynn Pettis (3/22/2010)
GSquared (3/22/2010)
tstaker (3/22/2010)
Anyone have anything funny, interesting or weird to talk about today? I'm bored.
My main subjects of conversation so far today have been politics (Obamacare passed...
"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
March 22, 2010 at 12:11 pm
As far as the process goes, I think you have it right. The only suggestion I can make is to script the process. I'd open up PowerShell and put 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
March 22, 2010 at 10:56 am
You can do the same with SQL Server 2005.
You also have the option of provide plan guides. Here's an introduction on the topic from Microsoft.
"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
March 22, 2010 at 8:56 am
Viewing 15 posts - 15,646 through 15,660 (of 22,219 total)