How did it help? What was the problem?

Never import directly to the final destination table... import into a staging table... should be able to use a default on a staging table but, if not, just update the...

Two way street here... please share your solution.

Heh... do you intend to print that size sheet?

Test the code in the presence of the indexes and not... that's the only real way to tell.

That's one of the best compliments anyone could ask for, James. Thank you, Sir!

14k characters? What on earth are you doing?

Still, Exec will handle many more than 14K characters... so that's not the problem. Can't tell what's causing the problem 'cause...

Please share what you did...

Both will take the same time because EM7 will run the same code as what you've typed behind the scenes...

Yes, thank you for the feedback and I agree that a clustered index will, in fact, make the concatenation run much faster... except that most folks aren't going to dedicate...

Well, kind of... before SQL Server 2000, there was no such thing as user defined functions... people ended...

Since there is no need for dynamic SQL in this case, just remove the quotes from the variable names... like this...

ALTER PROCEDURE spgetemp

@empname varchar(30),

@jdate datetime

AS

SET NOCOUNT ON

insert into #t exec...

Heh... Mom always said, "Never run with scissors"... being in a hurry on code has the same effect on careers.

Anyway, glad you figured it out... and thank for the feedback.

Awesome... thanks for the feedback, Derek!

Unless none of your dates have times on them, the original query and the replacement query are bad...