Then you're just a little bit stuck. You can't refer to objects that don't exist in the query, even if it's just in an IF statement. Why couldn't you use...

Depending on the data types in question, there's nothing inherently wrong with a compound natural key. I'm not sure why it would matter to the end user though.

If I understand the problem, then I'd suggest instead of having three queries for the three version, have three procedures and then, depending on the version, using your IF statement,...

I'm pretty similar in approach, Profiler is my bestest buddy.

After that, since you're in 2005, you can look at sys.dm_exec_query_stats for an immediate picture into which queries are running...

Absolutely. No issues at all.

It sounds like you can do this with a trigger or with a stored procedure. While I'm not a fan of triggers, if you need one, you need one. It...

Primarily because it's unreliable. Your time is better spent learning how to do indexing yourself...

Are the inserts & deletes done all the time or in discrete batches? If the latter, you can leave indexes off until you need them and then add them. If...

And you use this to reduce the number of calls back and forth between the stored procedure and the application calling it.

Also, by default, every proc exits with either a 0 for success or a 1 for failure as a return code on the proc. You can check for this in...

So, if you run the TSQl to create your function, you can't see it? Are you looking through the GUI? If so, make sure you're hitting refresh. If you can...

And here, the thread died, a horrible, messy death.

IT isn't going away any time soon. If it does, we'll be far to busy eating each other to worry about where a pay check is going to come from.

I guess I'm a bit in the middle. While, as an employee, I really don't want to see my job go away (really, seriously, I like my job, I need...

To really answer the question, you've got to post the execution plans.

When updated statistics, did you use the FULL SCAN option?