{"id":1135,"date":"2007-11-05T19:45:16","date_gmt":"2007-11-05T19:45:16","guid":{"rendered":"\/blogs\/paul\/post\/Conference-Questions-Pot-Pourri-2-Database-mirroring.aspx"},"modified":"2017-07-17T08:50:00","modified_gmt":"2017-07-17T15:50:00","slug":"conference-questions-pot-pourri-2-database-mirroring","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/paul\/conference-questions-pot-pourri-2-database-mirroring\/","title":{"rendered":"Conference Questions Pot-Pourri #2: Database mirroring"},"content":{"rendered":"

Sitting here in our Disaster Recovery class at SQL Connections and Kimberly’s on till lunch so I’m banging out a quick blog post covering the database mirroring (DBM) specific questions.<\/p>\n

Q1) Can I use IP addresses instead of server names when using the DBM Monitor?<\/strong><\/p>\n

A1)<\/strong> Unfortunately not.<\/p>\n

Q2) Is there any in-built throttling mechanism in DBM to allow the mirror to catch-up when synchronizing a synchronous mirroring session?<\/strong><\/p>\n

A2)<\/strong> Yes, if there’s more than 1MB of transaction log on the principal that hasn’t been sent to the mirror, the mirroring session state will be switched from SYNCHRONIZED<\/em> to SYNCHRONIZING<\/em> and the principal itself will start adding a few milliseconds delay to transaction commits until the amount of unsent log drops below 1MB<\/p>\n

Q3) Are there any tips when setting up a mirroring session using backups?<\/strong><\/p>\n

A3)<\/strong> Yes, make sure that all the backups are restored WITH NORECOVERY<\/em> on the mirror. The database has to be unrecovered otherwise the mirroring session cannot start and you’re back to square one with restoring the mirror database.<\/p>\n

Q4) What are the performance considerations with DBM – both in terms of the impact on the application workload and on DBM itself?<\/strong><\/p>\n

A4) <\/strong>Here are some links to resources that discuss this:<\/p>\n