Viewing 15 posts - 18,871 through 18,885 (of 22,219 total)
My rule of thumb is the same as Jeff's with one exception.
I've found some queries that are only, ever, doing a full scan of the temp table can run faster...
"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 6, 2009 at 5:48 am
If you think these queries are bad, you should see the stuff coming out of nHibernate. I've only seen a few so far, but they're pretty horrifying. It does implicit...
"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 5, 2009 at 6:25 pm
I expected it to perform the join inside a sub-select and then select from the result set as a single set of values. That would have helped explain why 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
January 5, 2009 at 11:55 am
I'm not sure, I haven't worked with Entity Framework much. What does it do when it has to do a JOIN between two tables?
"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 5, 2009 at 11:33 am
I'll bet the execution plan for both is the same.
It's a messy way to write procedures, at least for really simple things like this, but it's not going to add...
"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 5, 2009 at 11:00 am
Michael Earl (1/5/2009)
Eric Klovning posted a great response in this thread:http://www.sqlservercentral.com/Forums/Topic629445-145-1.aspx
It was a link to:
http://letmegooglethatforyou.com/?q=free+open+source+sql+schema+diff+tool
That gave me a really good laugh first thing this morning. I think that's a 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
January 5, 2009 at 10:55 am
Ah, I didn't go back and look at the execution plan again.
"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 5, 2009 at 10:52 am
Hey Jack,
Yeah, OPTIMIZE FOR is actually more than a little big dangerous. What happens when the underlying statistics change? You have to constantly review the work you did with it.
I...
"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 5, 2009 at 8:57 am
RBarryYoung (1/5/2009)
Actually, I heard from someone at PASS that WITH RECOMPILE does not work reliably for this problem in SQL2005, but "is fixed" in SQL 2008.
WITH RECOMPILE was never a...
"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 5, 2009 at 8:46 am
You can also use the OPTIMIZE FOR query hint as a way to force the plan down an optimal path.
"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 5, 2009 at 8:44 am
Or Jack.
Or you for that matter.
I might though.
"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 5, 2009 at 8:41 am
After migrating it's pretty strongly suggested that you update statistics with a full scan on all the tables in a database. Did you do this?
"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 5, 2009 at 6:55 am
I think Barry's right. It's probably parameter sniffing.
Compare both execution plans. See what's different between 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
January 5, 2009 at 6:48 am
Why do you need it to be in a single statement?
"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 5, 2009 at 6:45 am
Eric Klovning (1/5/2009)
you might try this:http://letmegooglethatforyou.com/?q=free+open+source+sql+schema+diff+tool
That's pretty cool. Gave me a laugh.
Just a suggestion on the original question, you might take a look at Red Gate's SQL Compare. It's not...
"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 5, 2009 at 6:42 am
Viewing 15 posts - 18,871 through 18,885 (of 22,219 total)