Viewing 15 posts - 20,821 through 20,835 (of 22,219 total)
2005 Plan cache is pretty radically different than 2000.
Take a look at at this blog by some of the developers from MS. It might help.
"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 18, 2008 at 11:52 am
Execution plans changed because of a recompile? That's a pretty likely possibility.
"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 18, 2008 at 11:08 am
Take a look at the OUTPUT clause as a mechanism to capture the data that is inserted as it gets inserted. This is much more effecient, as well as easier...
"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 18, 2008 at 7:41 am
If you want it to go into a temp table, this works fine (I used Adventureworks to test it):
SELECT ContactTypeID, [Name] INTO #mytem FROM Person.ContactType
union
SELECT StateProvinceID AS CultureID, [Name] 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 18, 2008 at 5:49 am
If you're getting multiple values from one table, you should probably apply some type of filter either in the ON statement of the join or in the WHERE clause. 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 18, 2008 at 5:37 am
After it gets applied, any impact is dependent on the number of rows inserted or updated against which an assertion for this constraint must be made. The more rows immediately...
"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 18, 2008 at 5:30 am
Just that when you set up a linked server its available to every database and every user (that has the password, assuming you don't cache it in the connection, making...
"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 17, 2008 at 1:28 pm
Steve Jones - Editor (3/17/2008)
I once got a resume with the "Interests" section saying "Eating exotic meats"
I wanted to bring the guy in just to see him, 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
March 17, 2008 at 12:54 pm
True. But based on what he had posted above I assumed he was already doing that much.
"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 17, 2008 at 12:49 pm
Not disagreeing, but I'd say the biggest tip would be to find some other method because they become a glaring security hole. But, if you absolutely, positively have to communicate...
"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 17, 2008 at 12:47 pm
Look up the topic "Linked Server" in the Books Online. That will get you started.
"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 17, 2008 at 11:59 am
Try running Profiler over that same period of time. You'll see what exactly is getting called. Be sure you capture before & after the event in case a process runs...
"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 17, 2008 at 11:33 am
You might wait a bit and see if anyone else posts anything else interesting here. You are working in an area where there is room for interpretation and others 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
March 17, 2008 at 9:03 am
Indianrock (3/17/2008)
"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 17, 2008 at 8:52 am
Yeah, that's a lively set of responses.
One thing that did come up over there that I should have raised, what are you using the schema's for? Is it to seperate...
"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 17, 2008 at 8:17 am
Viewing 15 posts - 20,821 through 20,835 (of 22,219 total)