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....

GilaMonster (9/22/2014)

---

If Field in Table1 is ever null, that query would return no rows. However since that's the primary key (I assume, since it's the reference for a fk), it's...

IF OBJECT_ID('tempdb.dbo.#sp_spaceused') IS NOT NULL

DROP TABLE #sp_spaceused

CREATE TABLE #sp_spaceused (

db_name varchar(100) NOT NULL CONSTRAINT sp_spaceused__DF_db_name DEFAULT '',

name varchar(100)...

You did add 70 rows, so while the growth is a little higher than average, it's not ridiculously high. Yes, you do want to convert to varbinary(max) instead of...

That "DISTINCT" is a big concern. Either the joins are producing dups, and thus the joins need modified, or the code is needlessly forcing SQL to sort the results.