Viewing 15 posts - 20,356 through 20,370 (of 22,224 total)
If your query execution timeout is set to zero ("0") in Management Studio, you shouldn't be seeing a 30 second timeout. Are these queries crossing servers in some way that...
"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
May 22, 2008 at 6:01 am
I'm not entirely sure, but three things come to mind. First, the engine & optimizer behave differently enough that in this situaion 32 is just better than 64. Second, differences...
"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
May 22, 2008 at 5:57 am
As others have already pointed out, to really answer the question you need to post some structures and some sample code.
But, taking a stab at it, it sure sounds like...
"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
May 22, 2008 at 5:41 am
Now, now... we're stepping outside the bounds of the experiment.
I'll have to see what I can do with a materialized view though. That's a good idea just to try out.
"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
May 21, 2008 at 2:13 pm
Or just use good ole' fashioned bcp.
"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
May 21, 2008 at 1:25 pm
Yeah. I'm actually working on comparing MAX, TOP and ROW_NUMBER. I was hoping to outline which might be better when.
"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
May 21, 2008 at 1:18 pm
Ah, partition by... crud. I was bouncing all around it and I just couldn't figure it out. That looks great. I tested it against the single row and large set...
"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
May 21, 2008 at 12:44 pm
You'll need to look at the queries being run and determine what the most likely access paths are for your data. There you'll want to put indexes. After that initial...
"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
May 21, 2008 at 9:58 am
Since backups are just from committed transactions, I doubt you can move the log in that manner. Can't the Log Explorer read from log backups directly? I'm pretty sure 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
May 21, 2008 at 9:01 am
Itzik was doing it on demand. It wasn't hard either. He just had to get the queries to run against similar sets of data and he could force the issue...
"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
May 21, 2008 at 8:45 am
Actually, according to Itzik Ben Gan and some pretty convincing tests (he gave the presentation at the last PASS Summit), NOLOCK can result in duplicate and incorrect data because 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
May 21, 2008 at 7:33 am
The short answer is, it depends. The longer answer is, that in some cases, yes, it makes a huge difference to put the filters into the JOIN instead of 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
May 21, 2008 at 6:38 am
Check the execution plan. I'll be you're seeing tons of table or index scans.
"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
May 21, 2008 at 6:23 am
You can't join outside the OUTPUT clause, but since you've put the records into a table variable (you might want to use a temp table for this instead) you can...
"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
May 21, 2008 at 6:18 am
Just to be a bit contrarian, I agree with Jeff & Gail on TableA, but on Table B, I'd look at making the foreign key value from TableA the leading...
"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
May 21, 2008 at 6:13 am
Viewing 15 posts - 20,356 through 20,370 (of 22,224 total)