Tried that... there's no way to trace the original colid of the base table to the colid of the columns in the view under a new name. This is...

Thank you for that... but I don't want you to waste anytime on something that won't be done .

It's already been suggested. Would be too much work to code what they needed and maintain the site that way (point system and all). So just say that...

What???

The will create an exact copy of the production db. Then using your in-house change management, redeploy the code to that db just like you would in the production...

Can't really help without the structure of the tables... also whta makes you think that the first and last name combinaison is unique across all the system (to match to...

And I forgot all the converts, functions....

That's impossible to do reliably without some text parsing... no wonder it's not included in the system views. The columns_usage doesn't reffer only...

Restore under a new name, then use your change management in place to deploy to that new db.

Something like this?

Select col1, col2 from dbo.Employees E inner join dbo.Customers C on E.FirstName like '%' + LEFT(C.ContactName, 3) + '%' and LEFT(C.ContactName, 3) = 'AN'

Dude, works with 2k... and most likely much earlier.

You forgot ", subqueries/derived table and other views... Still working on it but it doesn't look good.

Not the first time it happens... and certainly not the last .

You'd have to use difference. Check it out under bols it's pretty good, but I don't think it was made for such a task.

Sounds about right... make sure that the keys are all indexed and that'll be pretty all you can do to optimize this.

His name is peterhe. Enthusiast is just related to his number of postings.

You'll have to split it into its smaller parts for the task... and I suggest you do that for the db too. It's easier if you have the street...