Viewing 15 posts - 20,131 through 20,145 (of 22,219 total)
The optimizer, along with a whole of the rest of the engine, was changed between 2000 and 2005. It's not at all surprising that you'll see different execution plans 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
June 18, 2008 at 8:48 am
There's not a good source for this information. Experimentation is how I'm getting by.
I can recommend three sources that can help, in addition to posting here (althouth only 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
June 18, 2008 at 8:16 am
F'ing lovely. Worked perfect. Thank you.
Now what the heck did you do?:w00t:
"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
June 18, 2008 at 7:56 am
I think the frequency is also going to affect this. You would have to check often enough to catch the event as it occurs.
"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
June 18, 2008 at 7:44 am
Different people do it different ways. You can control the transaction from the application, but you need to be very cautious about getting extraneous code in the way 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
June 18, 2008 at 7:38 am
Sorry, I only posted part of the XML. It's the XML from an execution plan. Here's a section of the entire XML file (brackets replaced):
[ShowPlanXML xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Version="1.0" Build="9.00.3042.00" xmlns="http://schemas.microsoft.com/sqlserver/2004/07/showplan"]
...
"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
June 18, 2008 at 7:34 am
OK. It ran, but it's returning null for all the values and that's wrong. A little more help please?
"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
June 18, 2008 at 7:08 am
OK. I think I get why you're using the [1] twice in the first example, but what do the parenthesis do in the second?
Oh, and thanks for the help.
"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
June 18, 2008 at 7:06 am
You're stuck. You either need to move to 2005 & use VARCHAR(MAX) or stay in 2000 and use TEXT. There's no in between.
DB2 supports (MAX), but I'm not sure about...
"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
June 17, 2008 at 12:18 pm
Look into using the NODES method. Here's an example from BOL:
SELECT C.query('.') as result
FROM Production.ProductModel
CROSS APPLY Instructions.nodes('
declare namespace MI="http://schemas.microsoft.com/sqlserver/2004/07/adventure-works/ProductModelManuInstructions";
/MI:root/MI:Location') as T(C)
WHERE ProductModelID=7
"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
June 17, 2008 at 11:43 am
Congratulations. Good work.
"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
June 17, 2008 at 8:22 am
Provisional-DBA? But that'd be true & not funny.
Uhm... wanna-be-DBA?
"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
June 16, 2008 at 11:16 am
OK, but what did it mean?
"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
June 16, 2008 at 10:42 am
You're hitting a variation of parameter sniffing (here's Ken Henderson's description of parameter sniffing). Usually this is a good thing, but sometimes it isn't. Ken shows a method for 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
June 16, 2008 at 8:49 am
I'd suggest two things, first, get an estimated execution plan with the parameters and compare it to an actual execution plan without. Also, because you're setting your date values 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
June 16, 2008 at 6:55 am
Viewing 15 posts - 20,131 through 20,145 (of 22,219 total)