Try this:

SELECT COALESCE(fs.CustomerKey, fo.CustomerKey) AS CustomerKey

, COALESCE(fs.StoreKey, fo.StoreKey) AS StoreKey

, ISNULL(fs.LastWeek, 0) + ISNULL(fo.LastWeek, 0) AS LastWeek

, ISNULL(fs.LastTwoWeeks, 0) + ISNULL(fo.LastTwoWeeks, 0) AS LastTwoWeeks

, ISNULL(fs.LastThreeWeeks, 0) + ISNULL(fo.LastThreeWeeks, 0) AS...

No, such detailed change log info is not available. And when you think about it, you realize that it would be just too much overhead and disk space for...

I don't think you need to go thru all that. Just modify the original query to get what you need. Not a lot of details, but something like...

About the best you can do is to cluster the Costing table by date. That could help significantly when there are a limited number of lookups. For large...

You could adjust it to handle an address without a period / with only the top address specified (such as "10").

LEFT(IPAddress,CHARINDEX('.', IPAddress + '.') - 1)

In fact, the "property name" should not really be in the activity table, just the property_id that represents that property name.

You're assuming that every property name will be in the activity table. That may be a valid assumption for your particular data set up, I don't know. You'd...

I think this is simpler and will do what you need. You might want to tweak "<" to "<=", depending on exactly what you want the cutoff date to...

You'll need to use the "property master" table with a left join, something like below:

SELECT property_name, pa.activity_date

FROM properties p

LEFT OUTER JOIN property_activity pa ON

pa.property_name = p.property_name...

SQL won't automatically KILL running tasks.

Your best bet is to force them to recompile immediately. AFAIK, the only way to do that is to have it affect the entire...

Never use ISNULL() in a WHERE or in JOIN conditions. You can always code around it, and it causes optimizer issues. There are very few times when you...

You have to specific with terminology here. A deadlock is a specific type of blocking that cannot be resolved without canceling/abending at least one task. Blocking can eventually...

Yes. If the procedure was already executing, that execution would still use the old code.

It's currently the PK (perhaps). Just in case, I'd write the code so...

Of course the only ultimate solution to "replace bad vendor query" is "replace bad vendor." 😀

You can set up a trace with a high threshold(s) to capture really bad queries....