Viewing 15 posts - 18,646 through 18,660 (of 22,226 total)
GilaMonster (1/22/2009)
gyessql (1/22/2009)
select ...
from table t1
inner join t2
...
"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
January 22, 2009 at 10:09 am
Andrew Reilly (1/22/2009)
You need to watch out for any *= or =* joins in the where clause as this is no longer supported!
The Upgrade Advisor will catch that, as well...
"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
January 22, 2009 at 7:34 am
Me neither. Same things Gail said. Plus, 2005 offers a few things that improve performance, reducing contention, helping to prevent deadlocks.
"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
January 22, 2009 at 7:13 am
Oops. There I go again not reading everything before posting.
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
January 22, 2009 at 7:07 am
gyessql (1/22/2009)
select t1.*
from table1 t1
inner join table2 t2
...
"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
January 22, 2009 at 6:30 am
You also might consider using EXISTS rather than a count. It will work faster
IF EXISTS (SELECT * FROM TabA)
BEGIN
END
ELSE IF...
"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
January 22, 2009 at 6:18 am
Plese don't cross-post. This leads to multiple people attempting answer the questions in more than one location.
I have also posted an answer to this question here: http://www.sqlservercentral.com/Forums/Topic641528-149-1.aspx
"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
January 22, 2009 at 6:08 am
You really need to get the execution plans to understand where your bottlenecks are. It might be indexes or it might be TSQL or it might be your structure. Remember,...
"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
January 22, 2009 at 6:06 am
Built in to Management Studio is a way to view the diagram. Connect to a server. In the Object Explorer pane expand databases, pick a database and expand that. There'll...
"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
January 22, 2009 at 6:02 am
You can do an upgrade one of three ways, an inplace upgrade, as you've been discussing, a back up & restore or detach and attach. Any of the three 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
January 22, 2009 at 6:00 am
krypto69 (1/21/2009)
Is it possible that my non clustereds are hurting my (after the fact) choice of clustered?
Generally speaking, no, non-clustered indexes aren't going to hurt your clustered index, but...
"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
January 22, 2009 at 5:57 am
On another reading through the code, I think I'm going to eat crow and agree. That was a better approach and I'm wrong about it. I should have looked more...
"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
January 22, 2009 at 5:46 am
I've done it both ways and either will work, but in the long run, keeping the PK name the same throughout the structure seems to lead to less confusion.
"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
January 22, 2009 at 5:45 am
I'm inclined to say the second without any data. But I've seen instances where the first can be faster.
Testing and examining the execution plans are the only way to be...
"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
January 21, 2009 at 1:07 pm
They are two different things.
A trigger fires in response to either data manipulation, a DML trigger, or certain structural changes, a DDL trigger.
A stored procedure is a piece of TSQL...
"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
January 21, 2009 at 12:00 pm
Viewing 15 posts - 18,646 through 18,660 (of 22,226 total)