This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Custom Alert - best practice for a long running query?

I have a custom alert that runs daily, and the query takes about a minute. I noticed it was the victim of a deadlock recently, and I want to ensure that it will always be the victim. The target is SQL Server 2012.

Does DPA use a low priority session? Is there something I should do to ensure that my custom alert's query won't win in a future deadlock event?

There's little I can do to improve this particular query, and it's reading from a large table that can't be altered. I can't create new indexes on it; that would invalidate product support.

Thanks