Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
sp_blitz incorrectly excludes checks on EC2 VM with default name #1925
Version of the script
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
added a commit
Jan 18, 2019
Fixed. The dev branch now detects RDS by also looking for:
And then also adds a priority 0 (top) result noting that checks were skipped because RDS was detected. Also added that for Express Edition and Azure SQL DB Managed Instances while I was in there.
It is admittedly an edge case ha. From: Brent Ozar <email@example.com> Sent: Friday, January 18, 2019 6:39 AM To: BrentOzarULTD/SQL-Server-First-Responder-Kit <SQL-Server-First-Responder-Kit@noreply.github.com> Cc: Randy Knight <firstname.lastname@example.org>; Author <email@example.com> Subject: Re: [BrentOzarULTD/SQL-Server-First-Responder-Kit] sp_blitz incorrectly excludes checks on EC2 VM with default name (#1925) Awwww, c'mon, man, you're not even bothering to change your server names? ;-) Yeah, I bet I can reverse engineer it based on some of the system objects they put in. I'll spin one up and check. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#1925 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/APZVJhIcOXrwPLed2jkTtG7HvKFKVjK1ks5vEdybgaJpZM4aHGRe>.