I liked that !!!!

Sorry "ClueBat"

Scott, Glad you got the cached execution plan.

Now. If all you care is total time it takes I don't see why do you need to delete or truncate the temp table...

Sorry for the delay guys I was out to lunch ( Ihave to eat you know )

OK Glad that we could help you...

Just watch out for the limit of 8000 characters which at the pace you are going you may get there in no time ...

>>Oy... I suppose I could, I'll have to think on that one. That's a lot of dynamic sql. <<

You mean this ?

declare @str varchar(8000)

@str = 'insert into Appointments( ID, CarrierID)...

If the schema changes you can generate the SQL dynamically.

BTW: you are HARD CODING COLUMN POSITIONS too ( set @ColID=11 )

sorry I didn't tested that I have no sql on hand now but it was just a typo

coalesce is the right spelling

-- I...

and if the number of "good" records is large move them into the live table a chunck at a time and take transaction logs backup more frequently to let it...

Scott, Even though I can't see the trace and you posted partially what you believed is releveant I can confirm my suspissions.

1. @Px are PARAMETERS! therefore execution plan is cashed .

2....

and why are you using "USE" if you can always prefix the dbname to the table name ?

Time for me to .... A G R E E

select UserID

 , Coalsece(Min(case when FieldName  =  FirstName   then  FieldValue  end ),'') As FirstName

 , Coalsece(Min(case when FieldName  =  LastName    then  FieldValue  end ),'') As LastName   

 , Coalsece(Min(case when FieldName  =  Initial    ...

Can't you change that at client side ?

Eagerly waiting for poster reply