Viewing 15 posts - 15,826 through 15,840 (of 22,219 total)
Everything Steve said.
Plus, another way to cut costs is to volunteer for the PASS organization, bust your hump, and earn a free admission to the conference. It's not easy, 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
February 12, 2010 at 11:48 am
blandry (11/18/2008)
Do you ever take a moment and think about how many...
"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
February 12, 2010 at 6:24 am
Excellent article. Well written. Good advice. Practical and straight forward. Keep it coming.
"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
February 12, 2010 at 6:21 am
You have to take into account the fact that you are either instantiating a connection or pulling one out of the connection pool. This will also add some overhead 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
February 11, 2010 at 6:47 am
stephen.kuhl (2/10/2010)
Really? that's your answer? "hit microsoft there's tons of information there"gosh, what a well researched and helpful answer.
Read the question again. My answer, based on the question, is pretty...
"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
February 10, 2010 at 3:16 pm
The reason there probably aren't that many articles comparing performance between the two is because they're meant to substitute one for the other. INTERSECT is meant to find the distinct...
"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
February 10, 2010 at 11:19 am
Excellent. Glad I could help. Thanks for posting what the correct answer was too. It'll be useful if people searching for the same issue find this in the future.
"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
February 10, 2010 at 8:05 am
wschampheleer (2/10/2010)
Grant Fritchey (2/10/2010)
wschampheleer (2/10/2010)
Thank you for the compliment.
Unfortunately, I believe your new version is no improvement: you still need to insert the old ID if you want to retrieve...
"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
February 10, 2010 at 7:07 am
wschampheleer (2/10/2010)
Thank you for the compliment.
Unfortunately, I believe your new version is no improvement: you still need to insert the old ID if you want to retrieve it using the...
"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
February 10, 2010 at 6:50 am
sql_lock (2/10/2010)
In my example, no (as sql is just changes the pointers to the meta-data). But to answer with the original post in mind then yes you would need 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
February 10, 2010 at 6:26 am
Huge topic. Someone should write a book.
Execution plans, in short, are how SQL Server determines how it will access your data. They are reused if the query you're submitting matches...
"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
February 10, 2010 at 6:10 am
Test, test, test. Introducing constraints into a system that had none previously will, in all likelihood, lead to errors. Go slow. Try to identify the areas of data that are...
"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
February 10, 2010 at 5:59 am
You can only insert into one table at a time as far as the TSQL commands are concerned. But as the last post showed, if you wrap these inserts 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
February 10, 2010 at 5:55 am
sql_lock (2/10/2010)
You could try using the Switch command.
ALTER TABLE [dbo].tbl1 SWITCH to [dbo].tbl2
Don't you also have to set up partitioning between these tables first? I'm asking because I've never used...
"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
February 10, 2010 at 5:53 am
Another option is to use the OUTPUT clause to capture the generated ID's and then use them in the inserts in the second table.
"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
February 10, 2010 at 5:52 am
Viewing 15 posts - 15,826 through 15,840 (of 22,219 total)