andybrooke
asked on
Microsoft SQL Server 2008 R2 Replication
Hi,
current setup is MySQL with 2 servers running master to master replication. We are having to move to Microst SQL but want to keep a master to master setup.
We have been told that we need to use SQL Standard to have replication working correctly. Is this correct? As I've seen some replication guides online saying you need to use enterprise.
We want the replicating to be realtime.
Thanks
current setup is MySQL with 2 servers running master to master replication. We are having to move to Microst SQL but want to keep a master to master setup.
We have been told that we need to use SQL Standard to have replication working correctly. Is this correct? As I've seen some replication guides online saying you need to use enterprise.
We want the replicating to be realtime.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I agree with icohan, merge replication is what you need.
Not to make assuptions -your requirements are:
1.two servers with identical databases in different locations
2.the two servers both have data updates(read/write operations) on them that need to be synced.
3.the syncing between the two servers to be automated.
SQL Server standard Edition should cater for your needs.
Peer to peer replication can also work in this situation but then you'll need sql server 2008 enterprise edition which is more costly.
I can set up your servers if you want.
Not to make assuptions -your requirements are:
1.two servers with identical databases in different locations
2.the two servers both have data updates(read/write operations) on them that need to be synced.
3.the syncing between the two servers to be automated.
SQL Server standard Edition should cater for your needs.
Peer to peer replication can also work in this situation but then you'll need sql server 2008 enterprise edition which is more costly.
I can set up your servers if you want.
by the way Log shipping will not work because both instances need to be writtable.
in log shipping,one instances database will be in a recovery state and not writable.
in log shipping,one instances database will be in a recovery state and not writable.
ASKER
Norman yes your correct 2 servers in 2 locations, and we do need syncing but realtime. As Telephone calls are transfered between staff at both locations that need to see the same data at the same time.
So its merge replication or mirrioring I need?
Thanks
So its merge replication or mirrioring I need?
Thanks
It's merge as I mentioned
merge replication -mirroring will not work.
mirroring is designed for high availability,what you looking for is scalibility
mirroring is designed for high availability,what you looking for is scalibility
ASKER
and merge is real time? And both servers can wirte to the database?
Thanks
Thanks
Yes, merge replication is real time and all changes are sync-ed between all nodes part of the replication so all db's part of it will have the same data sfter it was replicated.
How Merge Replication Works: http://msdn.microsoft.com/en-us/library/ms151329.aspx
You need more time to recover from a failure if you implement Log shipping.
I deploy Log Shipping in two server with Standard versión and the difference time between the databases is 15 minutes.
I hope you find it helpful