can you explain what you mean? do you mean adding ODBC providers to your SQL instance? like adding Oracle, DB2...

lol except for aliases, we got the same solution!

Bliar thanks for posting what you found back; I updated my post, and PM'd Gianluca to make him aware of what you found;

I'm sure that this will help someone else...

something like this? i leave it to you to decide teh datediff period of time....i chose hours, you can change to days

/*--Results

rw ...

Ninja's_RGR'us (6/28/2011)

---

agreed...

another way to avoid the parameter sniffing is to use local variables as well: here's another example to consider.

CREATE PROCEDURE AVOIDSNIFFING(@Param1 int=0,@Param2 datetime = NULL)

AS

DECLARE @localParam1 int,

...

opc.three is right; I've done something similar with console apps and xp_cmdshell, as well as CLR.

no matter how you do it, it's outside of SQL...so it doesnt belong inside a...

with 17 parameters, no doubt most of them are optional....and might have default values? sounds like parameter sniffing...fast in SSMS with static values, compiled is slow.

search for "parameter sniffing" here...

yep i think muthukkumaran Kaliyamoorthy nailed it; someones in the database...maybe even you in the same or another SSMS window.

ALTER DATABASE MyDB

SET SINGLE_USER WITH ROLLBACK IMMEDIATE

I have no idea, and neither did the original poster;that's what i thought was so funny; i know it's a tool, but I cannot even...

asm1212 (6/27/2011)

---

Thank you so much Lowell...

That did it for me! Just for giggles: Can you explain that Row Number function and OVER PARTITION BY clause as it relates to these...

jbhauser (6/27/2011)

---

I am trying to utilize Gianluca's procedure (nice work by the way) against the corrupt databases found in the conference link above. I cannot get around the error "converting...

the WITh clause is a newer, fancy way of creating a temporary table...it's valid only for the next statement after the closing parentesis of the WITH;

so it's like saying CREATE...

oh yeah, that inner join:

inner join [MWLWEB].[dbo].[MWL_XY_Coordinates] Coord

if that join has more than one record for any thing it's joining to, you could get mulitple rows....so if there are...

you've got two SELECTS witha UNION, but only one of the selects have a WHERE clause...could that be it?

SELECT

[ToID] AS [ID],

[Origin City] AS [City],...