October 16, 2014 at 8:30 am
Excuse me if this is a foolish question but I'm not clear on some of the differences after reading TechNet docs.
Mirroring with async seems like a good option for pushing data from production across the country to a read only copy.
Log shipping also seems like a good option as well.
The problem is our database is rather large and copying it over the wire takes about two days.
So I can get a full backup, send it over the wire, and then send a few differentials, but is one option over the other going to be better with bringing the sync'd read only copy online and keeping it somewhat updated?
I am assuming, perhaps incorrectly, that replication is not ideal for this scenario as my goal is to just keep a distant server in read only mode up to date with a production OLTP database.
October 17, 2014 at 6:38 am
Maxer (10/16/2014)
Excuse me if this is a foolish question but I'm not clear on some of the differences after reading TechNet docs.Mirroring with async seems like a good option for pushing data from production across the country to a read only copy.
Log shipping also seems like a good option as well.
They are both acceptable although LS can have some latency based on the frequency of log restores
Maxer (10/16/2014)
The problem is our database is rather large and copying it over the wire takes about two days.So I can get a full backup, send it over the wire, and then send a few differentials, but is one option over the other going to be better with bringing the sync'd read only copy online and keeping it somewhat updated?
I am assuming, perhaps incorrectly, that replication is not ideal for this scenario as my goal is to just keep a distant server in read only mode up to date with a production OLTP database.
Bear in mind that if you want to use mirroring with async and readable then you'll need to create regular snapshots on the mirrored database. Both async and snapshot require enterprise edition or datacentre edition of SQL Server.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 17, 2014 at 4:44 pm
If you choose mirroring, you need to understand something about the read requirements, as to how up to date the data needs to be.
If latency is an issue and there will be long running queries run against the read only copy, you need to come up with a strategy for managing rolling snapshots and how clients reference them.
If there are substantial index rebuilds being done on the primary, then you may have substantial latency during and after those times.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply