How to replicate SQL Server logins and passwords to Cloud SQL
So, you’ve planned your database modernization journey. You’ve set up Google Cloud’s Database Migration Service (DMS), configured replication, and successfully synchronized your application databases from your on-premises or cloud systems to a fully managed Cloud SQL for SQL Server instance.
The replication is complete, the data is up to date, and you’re ready for cutover. But when your application attempts to connect to the newly migrated database, you’re hit with a frustrating roadblock:
Msg 18456, Level 14, State 1, Line 1: Login failed for user 'app_user.
The culprit is simple: your SQL Server logins didn't migrate with your database. In this post, we’ll look at why this gap exists, why it actually protects your organization's security posture, and how easy it is to bridge using standard, time-tested SQL Server tools.
Why DMS doesn't migrate logins: Security and compliance
Database Migration Service (DMS) is highly efficient at replicating database-level schemas and...
Copyright of this story solely belongs to cloud.google.com. To see the full text click HERE
