Comments
-
figured it out. Plans were forced on SQL 2016 and worked on SQL 2022 in 130 compat. After upgrading compat to 2022, the force plan was no longer valid, which caused the query hash to change.
-
Understood. Hopefully with what I have been able to put together so far will be adequate
-
Is there a definition anywhere in the dpa application files for the freemarker code that is used to construct [=dpa.body]?
-
This specific alert I was working on is for database wait time anomaly but am needing a template that will cover similar message text for other alerts. I think I found that the above message in the email alert comes from the variable [=dpa.body] which is I think is a custom compound variable that solar winds has…