Sure... saw the same thing... but I wonder if they could put a hardcoded "clue" in the Local Google Search to include "SQLSERVERCENTRAL.COM" or something like that...

P1naga...

Just for grins and because of the Left Outer Join to t1, try changing your from clause from this...

FROM

dbo.S_PRILSTITEM T1

INNER JOIN dbo.SPRILST T2 ON T1.PRI_D = T2.ROWD

LEFT OUTER...

For the most part, I agree... especially if you check out the I/O and all.

I was just reminiscing about when I first got to my "new" job 4 years ago......

Perfect... thanks for the feedback. And nice job, David!

Having 16 hours off is a rarity in this business 😉

Actually, both will do an index scan, I believe...

Yeah, you could... but who cares? So long as the code executes correctly, you may not need to see it.

Under {Tools}{Options}, click on the [Results] tab and see what...

The LIKE will be just a tiny bit faster in this case because it returns only the rows that have precisely 3 digits... the LEN()<9 will return things that have...

Heh... on the other side of the coin, how do you know it's not broke unless you try to fix it. 😉

You mean like doing the SELECT/INTO from a "derived" table with a "Top 100 Percent"... dunno... haven't tried that, but I will 😉

How are you viewing the code? If it's in Query Analyzer, it may just be a view setting under Tools Options.

You can concatenate about 256 8k variables for an...

I do wish they'd go back to a forum specific search...

See what I mean, Marcus? No... no one wrote 100% of the code you needed... but, unless I miss my guess, David's code will be very easy for you...

Sorry... I didn't say it quite correctly... if the table is preformed with an IDENTITY column, you'll be ok... it's actually when you use the SELECT/INTO with the IDENTITY function...

The table name cannot be variable without using some form of dynamic SQL... kinda like...

DECLARE @TableName SYSNAME

SET @TableName = 'sometablename'

EXEC ('SELECT * FROM ' + @TableName)

Thanks for the feedback, Matt...

I suppose the reason why I only got 40% improvement out of SELECT/INTO is because I'm running an "ancient" 5 year old P5 running at...