Itzik Ben-Gan just released a new book on TSQL Fundamentals. I can recommend that. Once you've got the fundamentals down, you might want to get his book called Inside Tsql...

You might want to pick up a copy of Itzik Ben-Gan's Inside SQL Server TSQL Querying. You're missing out on some core logical constructs as to how TSQL works and...

It's not anything I've heard of before.

I guess I need to go back to those 25 table joins that are running in under 50ms and start adding temp tables...

Nah. I'll stick with getting indexing right, and...

You're getting an error, as you stated above:

However when this query is executed it never completes, eventually failing with a message "8623: The query processor ran out of internal resources...

Oooh! Nice trick. I never knew about that one. Sweet.

And yes, '%y%' won't use an index. If you think about it logically, it makes sense. An index stores the key...

I've got two systems that we're trying it out on. The first one was getting lots of deadlocks. We know why, but we're not allowed to modify the code... Don't...

Actually, I meant:

I thought you summed it up nicely with those five.

If you...

You might want to be more lazy. You only needed five words in that last sentence.

Regardless...

Without, at the very least, three or four lines of qualification, that's a pretty lame post on just about any topic.

There must be increased sunspot activity or something because it sure seems like there's a bunch of these popping up all of a sudden.

If you want to program the extraction, say using C#, get the SMO (SQL Server Management Objects) loaded into your code and you can generate create procedures for any object...

And comma delimited IN statements are notorious. Like Gail said, execution plans & structures.

The last ON clause for Table 3 is the same as the ON clause for Table 2.

Is that the problem?