Many databases rely on login account credentials (Username, Password & SID) being identical between servers (ie. Availability Groups and databases involved in Dev-Test-Prod migrations).  This alert will check that all logins associated with Availability Group databases are identical between the AG servers. Additional logins can be added to allow for monitoring non-AG logins that need to be identical between servers (ie. logins associated with Dev/Test/QA servers).

Execute the 3 attached sql files (DDL, SP & Job) in the Minion Enterprise database.

Example Configurations:

An AG login account can be excluded from the alert by executing:

EXECUTE [CustomSetup].[LoginComparisonExceptions]  @AvailabilityGroupName = 'AG Name', @SourceServerName = NULL , @SourceDBName = 'MinionDefault' , @SourceLogin = 'Login Name', @SourceSID = NULL, @TargetServerName = NULL;

The default SA account on AG servers can be excluded by using its SID (if the login name is different between servers).

EXECUTE [CustomSetup].[LoginComparisonExceptions]  @AvailabilityGroupName = 'AG Name', @SourceServerName = NULL , @SourceDBName = 'MinionDefault' , @SourceLogin = NULL, @SourceSID = 0x01, @TargetServerName = NULL;

Additional logins can be added to the comparison check by inserting their information into the CustomConfig.LoginComparisonAccounts table. NOTE: The 'CheckPermissions' option is not active for version 1.0 of this alert.

INSERT INTO [CustomConfig].[LoginComparisonAccounts] ([SourceInstanceID] ,[SourceDBName],[SourceLogin],[TargetInstanceID],[TargetDBName],[CheckPassword],[CheckPermissions] ,[IsActive])

VALUES

(3,'MinionDefault','Login Name',4,'MinionDefault',1,0,1)

2017-06-21 version 1.0 (CheckPermissions option not enabled yet)