Enable-sqmMonitoringAccess | Sets up a monitoring account on all SQL Server instances of a computer. | v1.4.7.0 |
Export-sqmDatabaseLogins | Exports the SQL-authentication logins backing a database's users as a portable, self-contained T-SQL script (password hash + SID), for later application on a different, possibly unreachable instance via Import-sqmDatabaseLogins. | v1.9.78.0 |
Find-sqmADUser | Searches Active Directory for user accounts matching a SamAccountName wildcard pattern. | v1.9.9.0 |
Get-sqmADAccountStatus | Checks the status of an Active Directory user account. | v1.0.0.0 |
Get-sqmADGroupMembers | Lists all members of an Active Directory group. | v1.4.2.0 |
Get-sqmADGroupMembersRecursive | Lists all members of an Active Directory group with controlled recursion depth. | v1.5.1.0 |
Get-sqmADMemberGroups | Finds all Active Directory groups that contain a specified user, group, or computer. | v1.5.1.0 |
Get-sqmDbOwnerRisk | Finds databases where non-dbo principals are members of db_owner and reports the associated privilege-escalation risk as a pass/fail (green/red) HTML report. | v1.9.108.0 |
Get-sqmLoginLastAccess | Determines the last known access per SQL Server login. | v1.9.25.0 |
Get-sqmLoginPermissions | Lists all logins with their server- and database-level permissions. | v1.9.25.0 |
Get-sqmLoginSettings | Shows all logins with their default database and language setting. | v1.4.7.0 |
Get-sqmSaLogin | Resolves the current name of the built-in sa login (SID 0x01) on a SQL Server instance, even if it has been renamed. | v1.0.0.0 |
Get-sqmSysadminAccounts | Retrieves all logins with sysadmin rights on a SQL Server instance. | v1.0.0.0 |
Grant-sqmTemporarySysadmin | Grants an AD login temporary sysadmin rights for X days and automatically revokes them afterward via a self-deleting SQL Agent job - failover-robust across all replicas for AlwaysOn. | v1.8.1.0 |
Import-sqmDatabaseLogins | Applies a login-password/SID export produced by Export-sqmDatabaseLogins against a destination instance, then repairs any remaining orphaned database users. | v1.9.78.0 |
Invoke-sqmLoginAudit | Comprehensive audit of all SQL Server logins on one or more instances. | v1.0.0.0 |
Invoke-sqmSaObfuscation | Obfuscates the SA account on a SQL Server instance by renaming it, disabling it, and setting a random password. | v1.0.0.0 |
Invoke-sqmTempSysadminAction | Performs the actual sysadmin grant or revoke on ONE instance - optionally creates a missing AD login, removes it again on revoke, and optionally deletes the calling SQL Agent job after success (self-deleting job). | v1.8.1.0 |
Register-sqmAuditSession | Creates (if missing) and starts a dedicated Extended Events session that covers the "audit problem": login success/failure, database create/drop, and schema/metadata changes. | v1.9.115.0 |
Remove-sqmAdOrphanLogin | Removes Windows logins whose Active Directory account no longer exists (AD orphans). | v1.4.7.0 |
Repair-sqmDbOwnerRisk | Removes unexpected db_owner members and replaces them with db_datareader, db_datawriter, and a custom db_execute role granted EXECUTE on all stored procedures. | v1.9.108.0 |
Restore-sqmSysadminAccess | Emergency recovery when no working sysadmin login is left: stops the SQL service, restarts it in single-user mode, uses the one allowed connection to create/reset a login and grant sysadmin, then always restores normal multi-user operation. | v1.9.85.0 |
Set-sqmDatabaseOwner | Sets the owner of one or more databases to a uniform login. | v1.0.0.0 |
Sync-sqmDatabaseLogins | Synchronizes the SQL-authentication logins backing a database's users from a source to a destination instance in one call, for the case where both are reachable from the same session. | v1.9.78.0 |
Test-sqmLoginGroupAccess | Diagnoses why a user cannot log in when logins are provisioned as AD groups. | v1.9.119.0 |
Unlock-sqmSqlLogin | Unlocks a SQL-Auth login locked out by CHECK_POLICY - either without touching the password at all (via the documented CHECK_POLICY off/on toggle) or with a real password reset - and verifies CHECK_POLICY/CHECK_EXPIRATION are unchanged afterward either way. | v1.9.105.0 |