April 3, 2014 at 1:51 pm
So we are looking at a master/slave DB setup on the same server. There will be hundreds of thousands of records being inserted at times into the master along with databases and schemas being constantly created. So I would need to make sure the replication process can handle large inserts and table/schema creation. What's the best way to do this? I'm running 2008 R2 Standard. Connections to the slave DB will require read-only access meaning there will be no writes.
I was thinking about maybe doing hourly snapshot replication.
April 3, 2014 at 2:02 pm
If your database is small, your hourly snapshot will work fine. But if it's large, you may end up with creating snapshot for all your one-hour time frame. That's because snapshot replication uses BCP out/in. If this is a case, you may try Log shipping.
April 3, 2014 at 2:18 pm
I was thinking of log-shipping too but I don't like doing log-shipping with standby. I might go to the requestors and ask if I can change the synchronization timeframe to maybe 3 hours instead of 1.
April 3, 2014 at 2:21 pm
Also, we're talking about potentially replicating up to 50,000 tables. Don't ask, it's a long and painful story that I'm still peeved about.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply