Viewing 15 posts - 19,996 through 20,010 (of 22,219 total)
That sure sounds like homework.
Generally, for homework type questions, most of us ask that you post what you've tried to do and where you're having problems. That way we're helping...
"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
July 11, 2008 at 7:01 am
Michael Earl (7/11/2008)
As far as performance. The optimization engine will generate the same execution plan for equivalent queries regardless of which syntax you use.
Not for OUTER JOINS though. With...
"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
July 11, 2008 at 6:58 am
rbarryyoung (7/11/2008)
Grant Fritchey (7/10/2008)
There's an "Anti-Rbar Alliance"?How do you join? ...
Uhhhm, .. do you want it in SQL-92 syntax or SQL-89 syntax?
😀
You know, either way works for me, just put...
"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
July 11, 2008 at 6:39 am
Christian Buettner (7/11/2008)
what makes you sure this time that it does not make a difference?
Did you get this information from Microsoft ?
I am pretty sure that I had examples...
"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
July 11, 2008 at 6:38 am
Well, eliminating all the excess JOINS does improve performance threefold in this example, so I think you can reasonably expect the something similar with larger data sets.
Because of the OR...
"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
July 11, 2008 at 6:35 am
I've got nothing. The examples I thought I had, I can't find.
My heartfelt apologies for putting out bad information. For an INNER JOIN, it really makes no difference in terms...
"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
July 11, 2008 at 5:45 am
I probably won't have the example, assuming I can find it, until tomorrow. I'm looking though.
I did find this in the BOL
This sequence can sometimes influence the results 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
July 10, 2008 at 1:59 pm
I'm going to start digging, but I've had instances where moving filtration from the WHERE clause to the ON clause does change the execution plan. I don't have the example...
"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
July 10, 2008 at 1:23 pm
There's an "Anti-Rbar Alliance"?
How do you join? How much are the dues? Does the initiation involve sheep or goats?
"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
July 10, 2008 at 12:48 pm
You got it essentially right. SQL Server 2000 support ended... in May I think. That's main stream support. You can still pay to get access to PSS. The same thing...
"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
July 10, 2008 at 11:29 am
I sure don't mean to start a fight with my next statement....
Please don't do that. Learn to use the ANSI joins. There are a ton of good reasons. I'll give...
"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
July 10, 2008 at 11:26 am
Hmmm... I just ran the test and received no difference between truncate and delete.
"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
July 10, 2008 at 8:47 am
I think you're looking for something like this:
select c.date
from spdqty as c
inner join (select date, vialsOUT from spdqty) as a
on c.date = a.date
inner join (select date, vialsIN from spdqty)...
"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
July 10, 2008 at 8:28 am
So, you've got two tables that have three different and distinct relationships between the tables? I'm pretty sure that violates one of the rules of normalization, but I'm not sure...
"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
July 10, 2008 at 7:40 am
160gb is not small, but I've used Profiler (in a limited fashion) back in 7.0 on 300gb databases. That was before the improvements to the tool in 2000. You should...
"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
July 10, 2008 at 7:17 am
Viewing 15 posts - 19,996 through 20,010 (of 22,219 total)