July 9, 2013 at 10:29 am
I'm trying to decide between log shipping and replication for using a secondary database for reporting purposes. They want to have a secondary database for use as a reporting database. They're OK with the databases being 30-60 minutes out of sync. I was thinking about log shipping but I can't kick the users out when the logs are restoring. Now I'm thinking about using snapshot replication but I don't know if 30-60 minutes is too often for snapshots to be recreated. The database is about 25G. Should I just use transactional replication? Any thoughts would be greatly appreciated.
July 10, 2013 at 12:16 am
Transnational Replication might do the job but if the primary database is going to be updated with new tables and columns then this could become a problem since it would not sync unless you add as an article and also it will add identity columns to all of these so i feel that you can use mirroring and snapshot it on the reporting server and this way you can snapshot whenever you need the latest.
July 10, 2013 at 9:11 am
I was thinking of transactional replication as well. I was going to do snapshot replication as a temporary fix and then implement transactional later. Mirroring plus snapshots is a good idea but we only have SQL 2008 Standard so we can't create snapshots. Thanks for the input!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply