Viewing 15 posts - 17,911 through 17,925 (of 22,226 total)
It really depends on what you need to do. Let's assume a row into each table. You create a proc with variables for each of the columns, except the two...
"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 27, 2009 at 9:35 am
CTRL+2 in a query runs sp_who by default. You can change that.
It sounds like you were hitting CTRL+2 to open a table? I've never seen that done before. If 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
March 27, 2009 at 9:29 am
They add to the overhead. I use them occasionally when debugging, but always comment them out.
However, I've never tested them to see what the exact cost is.
You can get...
"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 27, 2009 at 9:22 am
Jeff should do it.
"Pork Chops for the DBA" by Jeff Moden
"SQL Server Performance Tuning by Pork Choping Deveopers" by Jeff Moden
"Better Performance by True Set Based Operations and Pork Chops"...
"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 27, 2009 at 8:43 am
suhasini.m (3/27/2009)
SELECT * FROM Table1
JOIN Table2
ON Table1.Column1 = Table2.Column1
SELECT * FROM Table1
JOIN Table2
ON Table1.Column1 = Table2.Column1
AND Table1.Column2 = XXX
Both these query returns same number of results say...
"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 27, 2009 at 8:38 am
Yes, they are very handy, aren't they?
"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 27, 2009 at 6:32 am
Just a side note, it's almost always a last resort to start applying blocking through hints. SQL Server is generally much more capable at handling it's locking and blocking processes...
"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 27, 2009 at 6:23 am
mazzz (3/27/2009)
So the order in which I'd reorg indexes would not be important then, I expect?
The tables are reasonably small (generally under 20000 rows), so I'm going to monitor...
"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 27, 2009 at 6:18 am
I'd dig into the performance monitor counters, cpu, I/O, etc. Especially focus on the waits and queues to see what things are slowing down for on the server. Here's an...
"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 27, 2009 at 6:15 am
That's a very broad topic. Here are a few of my personal pointers
1) Pick the clustered index first and pick it carefully
2) Keep the clustered index as narrow as practical...
"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 27, 2009 at 6:05 am
You have 4gb of memory on a production box running both SQL Server 2000 and SQL SErver 2005? I'd be willing to bet you're seeing serious memory pressure and probably...
"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 27, 2009 at 6:00 am
What made you choose those 12 fields? Were you working from a query plan or missing index information or recommendations from the Tuning Advisor?
You need to look at the execution...
"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 27, 2009 at 5:58 am
No, I don't think it rearranges the nonclustered indexes.
If you're doing large scale loads, you might want to drop the indexes & recreate them after the load because a large...
"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 27, 2009 at 5:50 am
Jeff Moden (3/26/2009)
Grant Fritchey (3/26/2009)
Bob Hovious (3/26/2009)
YOU are Mr. 3000.
In honor of this momentous occasion, you get to buy beers for...
"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 26, 2009 at 7:52 pm
Alvin Ramard (3/26/2009)
Jeff Moden (3/26/2009)
Grant Fritchey (3/26/2009)
Bob Hovious (3/26/2009)
YOU are Mr. 3000.
In honor of this momentous occasion, you get to buy...
"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 26, 2009 at 7:51 pm
Viewing 15 posts - 17,911 through 17,925 (of 22,226 total)