Viewing 15 posts - 17,731 through 17,745 (of 22,219 total)
It's not the same query if you've changed the code.
However, yes, with the same code, same data, same statistics distribution (you won't get the same statistics) you could get different...
"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
April 14, 2009 at 11:31 am
Is it a table valued UDF or inline scalar? If it's table valued, that might the core issue righ there. And no, that's not unique to 2005.
Even if it's inline,...
"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
April 14, 2009 at 8:56 am
If you want to get some idea as to why it works differently between 2000 & 2005, get the actual execution plan and see what SQL Server is doing 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
April 14, 2009 at 7:46 am
John Deupree (4/13/2009)
1. Would you consider this DB to be a relational DB, albeit poorly designed?
It's relational. I don't know enough to say it was poorly designed, but eliminating FK's...
"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
April 14, 2009 at 7:43 am
If you're running a query through a linked server, most of the time, all the data is moved across the wire first, then filters & joins are done to extract...
"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
April 14, 2009 at 7:38 am
I'd have to say it falls into it depends. I don't mind reading a bit, but sometimes people post several hundred lines of code and, quite frankly, I don't want...
"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
April 13, 2009 at 9:01 pm
That sure sounds like a pretty standard INNER JOIN.
Try this:
CREATE TABLE #Parent
(ParentId INT IDENTITY(1,1) NOT NULL
,Val NVARCHAR(50) NOT NULL
,CONSTRAINT pkParent PRIMARY KEY CLUSTERED (ParentId))
CREATE TABLE #Child
(ChildId INT IDENTITY(1,1) NOT NULL
,ChildVal...
"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
April 13, 2009 at 7:06 am
DISTINCT is killing your peformance. You should try to find away around it. Plus, from the execution plan provided, it was five rows going in and five rows coming 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
April 13, 2009 at 6:58 am
If your page life expectancy is high, there's not to do but sip some coffee and look for other causes of poor performance. A high page life means that 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
April 13, 2009 at 6:11 am
Someone or some process such as a SQL Agent job must be switching it to simple recovery. I'm not aware of anything that does it automatically in the background.
Which model...
"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
April 12, 2009 at 6:51 am
Darn. And I'm hungry too. Ah well. Life is full of these little disappointments.
First round of scotch is on me!
"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
April 11, 2009 at 3:14 pm
I agree with the others but feel the need to express it a different way.
If you're simply learning SQL Server, no. It's conceptually beyond the basics a bit.
If you're using...
"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
April 11, 2009 at 3:11 pm
I think my issue with doing it the "interesting" way as opposed to using JOINs is that, while this time, the performance and plan is likely to be identical, far...
"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
April 11, 2009 at 3:04 pm
Jeff Moden (4/11/2009)
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
April 11, 2009 at 2:58 pm
radek (4/11/2009)
Hi,
really you need all columns (*)
So you can create nonclustered index on macaddress is key of index and this index will have inlcude other colums, try 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
April 11, 2009 at 9:29 am
Viewing 15 posts - 17,731 through 17,745 (of 22,219 total)