New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Easier troubleshooting for forced plan failures #3309
Comments
To get a check like this into Blitz, I think you'd need something along these lines. I had most of this already in place from QuickieStore, I just haven't had a chance to consolidate it until now.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The "Automatic Tuning" (aka regressed plan forcing) in Azure SQL DB & SQL Server can go awry, leaving behind plan guides that fail and repeatedly recompile.
I'd like to have a better way to find out that:
Describe the solution you'd like
TBD. Today's issue was in Azure SQL DB, and I don't use sp_Blitz in Azure SQL DB. It may be time to do a separate sp_Blitz for Azure SQL DB with all of the foreachdb checks ripped out and converted into current-database checks, but that's a separate issue.
Describe alternatives you've considered
Manual troubleshooting like I did today. Dang, Query Store failures were the last place I thought of looking, and I burned 4 hours before discovering it was on fire.
Are you ready to build the code for the feature?
Yep.
The text was updated successfully, but these errors were encountered: