SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Multi Master Replication and Mirroring


Multi Master Replication and Mirroring

Author
Message
SKP DBA
SKP DBA
SSC-Enthusiastic
SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)

Group: General Forum Members
Points: 189 Visits: 55
Dear Experts,

I have requirement in my company that previously we are using HQ database to access application in another Main Branch.Now Requirement is that

1- HQ Server 1 HQ---> Separate SQL Database
2- MAIN BRANCH SERVER 2 ----> Separate SQL Database
Due to performance we are doing distributed database but we need to synced together if any user did change then no conflict will occur in both SQL database . If any of the server will down then all user will routed to Available SQL Server instance.


--> Current Environment SQL Server 2008 R2
--> Expected we Can also move to 2012 or 2016 if it is not possible in SQL 2008 R2 or if it is easy in 2016.

Current Solution
-----------------------
Server 1 -Mirroring(Server 2)
Server 2--Mirroring (Server 4) and in both Server 1 and Server 2 we will do Peer-2-Peer replication.

Please advise best solution with low effort and maintenance.

Thanks
SKP
Joe Torre
Joe Torre
SSCertifiable
SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)

Group: General Forum Members
Points: 6188 Visits: 1141
If you can upgrade and use Always On, that would be better for a number of reasons.
SKP DBA
SKP DBA
SSC-Enthusiastic
SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)SSC-Enthusiastic (189 reputation)

Group: General Forum Members
Points: 189 Visits: 55
Dear Thanks for the reply currently i have single instance and it is used in two branches due to network application is working slowly so we will do separate servers setup. Both Branches will use database and it will synchrise my question is that.

Current Environment SQL Server 2008 R2

If i use Always on with Peer-2-Peer replication then which version of server i need to migrate about my needs. SQL Server2012 or 2014 or 2016.
I checked mirroring is also available in 2012 and 2014.

My question what is the major reason to move on Always on because mirroring is also available in SQL Server 2012.

Please advise
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search