Tag Info

New answers tagged

0

We found the issue. It is a bug in SQL Server. When we set READ_WRITE the command is not transfeered properly into the mirror DB. When script start change partitions on the mirror server an error occured. After that the syncronization is ruined and the DB on the mirror is locked (in suspended state). We fix the issue by updating SQL Server to the latest ...


0

This should work as it did for me: Set the -failoverpartner using the mirror name in the sql agents for replication. Fail mirror over to secondary Make sure replication continues to send commands to subscriber. Remove mirroring so primary is no longer connected. Go to distributor, add an alias (sql server alias) The alias should be the old principal name ...


0

Actually, everything stayed the same, I found out that the service account some how lost the CONNECT permission. So, I gave the service accounts the CONNECT permission and all the mirrored database synced as expected!


1

As stated in Monitoring Database Mirroring MSDN You can monitor a mirrored database during a mirroring session to verify whether and how well data is flowing. To set up and manage monitoring for one or more of the mirrored databases on a server instance, you can use either Database Mirroring Monitor or the sp_dbmmonitor system stored procedures. A ...


0

I think I would first outline something like this before testing it while recording time with a stopwatch. D-X get the newProd and newMirror ready (OS + SQL Server + User Account, job, ...) build scripts for every step (back, restore, mirror, ...) D-3 add a new IP to oldProd update DNS with new IP and TTL = 300s (Time To Live) D, H-2 or H-1 (I assume ...



Top 50 recent answers are included