Logins compared: 6 | Mismatched: 2
| Login | Type | Present On | Missing On | SID Match | Password Hash Match | Default DB | Language | Status |
|---|---|---|---|---|---|---|---|---|
| app_orders_svc | SQL_LOGIN | SQLNODE01, SQLNODE02 | - | Yes | Yes | AG_TestDB | us_english | OK |
| DOM\svc-sql | WINDOWS_LOGIN | SQLNODE01, SQLNODE02 | - | Yes | n/a | master | us_english | OK |
| reporting_ro | SQL_LOGIN | SQLNODE01 | SQLNODE02 | n/a | n/a | AG_TestDB | us_english | Missing on secondary |
| etl_service | SQL_LOGIN | SQLNODE01, SQLNODE02 | - | No | Yes | AG_TestDB | us_english | SID mismatch |
| DOM\dba-team | WINDOWS_LOGIN | SQLNODE01, SQLNODE02 | - | Yes | n/a | master | us_english | OK |
| legacy_import | SQL_LOGIN | SQLNODE01, SQLNODE02 | - | Yes | Yes | AG_TestDB | us_english | OK |
A SID mismatch means the same login name resolves to different security identifiers on each replica - typically the result of dropping and recreating the login on one node only, and will make cross-replica permissions inconsistent after failover.