...and it would be a lot faster if you used BULK INSERT or BCP...

That's not such a bad idea (ad hoc usage to solve a very specific problem)... what is a bad idea is using non-temptable names for everything that you would normally...

Heh... small world we live in, huh?

Thanks for the great feedback, Ian... especially about keeping it casual (ie. fun) and the remarks about documentation... We've actually put sime "documentation standards" into play at work. They're...

Heh... I was thinking the same thing... beating are fun especially when delivered by code...

Since it's 2k5, I wonder if you could add a schema trigger to TempDB to sweep...

Speaking of testing... if you value your production system, now would be a good time to setup a testing twin so you can do full regression testing of the SP...

Just my experience... I keep a Tally table of 11k rows... sure, it covers the usual split of a VARCHAR(8000) but I use it for much more... if you consider...

Have you taken the time to verify that you actually have the problem?

Dunno about that... but I do know that throwing indexes at tables will absolutely not help code that is written incorrectly because the code will not be able to use...

Perfect... thanks for the feedback.

Yeah, anytime you have a join on different datatypes, it must do an implicit conversion to do the join... best you can get out...

You see the need to split a parameter with more than a million characters?

It will only show some pointer information in the Grid mode... you must be in the Text mode to see the data from a Text datatype.

Best thing to do would...

If you feel that you must split application code to make it easy to find, create a new database for each application... store only code and definition tables in these...

Heh, heh... in my shop, yes... 😛

Check the following URL... someone made the terrible mistake of naming tables and objects after customers and now he's in a bit of trouble...

http://www.sqlservercentral.com/Forums/Topic439936-5-1.aspx

Do...

This will do it... could turn it into a function...

DECLARE @PurchaseReqNo VARCHAR(50)

SET @PurchaseReqNo = '12,241,342,34234'

DECLARE @TempTab TABLE (Element INT IDENTITY(1,1) PRIMARY KEY CLUSTERED, ReqQty INT)

INSERT...