sp_Blitz: shows redundant results for RDS server triggers and tables

[yoni-yad2]

Version of the script
2025-07-04

What is the current behavior?

CheckID: 11

Server Trigger [rds_alter_database_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.
Server Trigger [rds_audit_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.
Server Trigger [rds_create_database_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.
Server Trigger [rds_create_login_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.
Server Trigger [rds_credential_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.
Server Trigger [rds_das_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.
Server Trigger [rds_deny_backups_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.
Server Trigger [rds_drop_database_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.
Server Trigger [rds_drop_login_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.
Server Trigger [rds_extended_events_trigger] is enabled.  Make sure you understand what that trigger is doing - the less work it does, the better.

CheckID: 27

The rds_component_version table in the master database was created by end users on Nov 14 2023 11:42AM. Tables in the master database may not be restored in the event of a disaster.
The rds_database_tracking table in the master database was created by end users on Nov 14 2023 11:42AM. Tables in the master database may not be restored in the event of a disaster.
The rds_failover_tracking table in the master database was created by end users on Nov 14 2023 11:42AM. Tables in the master database may not be restored in the event of a disaster.
The rds_master_files_tracking table in the master database was created by end users on Nov 14 2023 11:42AM. Tables in the master database may not be restored in the event of a disaster.
The rds_track_change table in the master database was created by end users on Nov 14 2023 11:42AM. Tables in the master database may not be restored in the event of a disaster.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Objects with prefix rds_ should be ignored by sp_Blitz

Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
SQL Server 2019 on Amazon RDS

[yoni-yad2]

Also, all checks on database rdsadmin are redundant as users don't have control over it.

[BrentOzar]

OK, great! Did you plan to submit a pull request to change these? This would definitely be a pull request we'd be interested in merging.

[BrentOzar]

I haven't heard back from you in a couple of weeks, so I'm going to go ahead and close this. If you want to resubmit the pull request with just the relevant changes, though, we'd welcome it! If not I understand, everybody's busy.

[BrentOzar]

Thanks for the pull request! Looks good, merging into the dev branch, will be in the next release with credit to you in the release notes.