sqlmigration-security-reviewlisted

Audits the security-object migration plan for a SQL Server move with 15 checks (J1-J15) — logins, server and database permissions, credentials, certificates/keys ownership, and Central Management Server registrations. Use this skill when a user is migrating a SQL Server database or instance and needs to carry over logins, permissions, credentials, or certificates, or asks "will my logins still work after migration" or "how do I migrate permissions." Trigger whenever security-object portability during a migration is the topic; dispatched here from /sqlmigration-review for the security-object family.
vanterx/mssql-performance-skills · ★ 5 · API & Backend · score 77

Install: claude install-skill vanterx/mssql-performance-skills

# sqlmigration-security-review ## Purpose Reviews the security-object family of a SQL Server migration — the slice `sqlmigration-review` dispatches here rather than checking itself. This skill owns 15 checks (J1–J15) covering whether logins, server/database permissions, credentials, certificate/key ownership, and Central Management Server (CMS) registrations will survive a backup/restore or log shipping/Always On AG seeding migration, and what breaks if they don't. - **Login Portability (J1–J5)** — orphaned users after restore, SID mismatch, login type unsupported on target platform, password policy differences, default database missing - **Permission Fidelity (J6–J9)** — server-level role membership, database-level role membership, explicit GRANT/DENY statements, ownership chains crossing the migration boundary - **Credentials & Secrets (J10–J12)** — SQL Server Credential objects, proxy account mapping, linked server stored logins - **Certificates & Keys (J13–J14)** — certificate/key migration for objects that depend on them (excluding TDE, which is `sqlencryption-review`'s domain), backup of certificates before cutover - **CMS (J15)** — Central Management Server registration entries pointing at the old instance name All fix recipes use native T-SQL system views (`sys.server_principals`, `sys.database_principals`, `sys.credentials`), the in-box `SqlServer` PowerShell module, and the native `sp_help_revlogin` script — no third-party module is referenced or require