asked
what are the frequent issues we facing on mirroring?
Hi All, i'm new to mirroring, So can any one mention what are the frequent issues we are facing in mirroing and at the time configure the mirroring also? Just a count of replies on this question and will share our experiances what issues faced and how we solved it?
Are this question and this one
http://ask.sqlservercentral.com/questions/108110/what-are-the-frequent-issues-we-facing-on-logshipp.html, homework or interview questions? Just so we can tag appropriately.
Interview questions you're going to be asking or ones you've been asked? If the latter, you should let us know that. We don't want to help people cheat their way into jobs.
The site does run on votes. So please mark all helpful answers by clicking the thumbs up and if any one answer lead to a solution mark that by clicking on the check mark.
1. when there is a network then mirroring endp piont needs to be restarted (in SQL Server 2008 no need to do it) 2. installing Service Packs while installing SQL Server or windows patching 3. adding a ndf file to the primary Server 4. moving databases between the Drives 5. shrinking the log(ldf) files
please have a look into this link [
http://sqlservr.blog.com/2011/12/29/database-mirroring-in-simple-steps/][1] [1]:
http://sqlservr.blog.com/2011/12/29/database-mirroring-in-simple-steps/
That's just explanation of how to configure the mirroring and it's good one... But Can you creat an issue and give the solution with how to comeout of it for the following points which you mentioned in above... 1.when there is a network then mirroring endp piont needs to be restarted (in SQL Server 2008 no need to do it) 2.installing Service Packs while installing SQL Server or windows patching 3.adding a ndf file to the primary Server 4.moving databases between the Drives 5.shrinking the log(ldf) files
A big issue I've seen is when developers use tables in the database being mirrored for temporary work rather than using temp dB. Since the transaction must commit on the mirror before the primary there is unnecessary data being sent across the network and this increases the duration of your transaction. Another issue is using under-powered hardware for the mirrored instance. Again avoidable delays are introduced. A quick rule of thumb is that every transaction will take twice as long to complete when participating in a mirror partnership.
As per the first point it's asynchronous mirroring right? If Yes I didn't get why you draged tempdb into picture..? And another question if transaction failed in Mirror how it will be roolback in Principle? Can you give me an explanation with example or some shat brief
Miiroring is generally synchronous unless using Enterprise Edition.
17 People are following this question.
