I am setting up a Reporting database that is a replica of the production DB. The environment is Win Server 2008 and SQL Server 2012 Standard. The product is DNN based. Right now Transactional Replication is used and it works but there
are some issues with it namely tables missing primary keys and upgrading DNN is a royal pain not to mention that the schema changes with every upgrade. I was thinking of setting up Log Shipping instead of Replication. The plan is to Log ship to
another instance and create two reporting databases that will be restored in turn. One of the databases will always be live and the other restoring. The restoring will be done in round robin fashion. The reporting server will query
the config database to find out which database is live. A service will be running on the Reporting DB server that will receive the next Log backup and will restore it over the inactive database. Once the restore is complete the configuration will
be updated to reroute all new reporting connections to the newly restored database. The component will then wait for the existing open connections to complete on the primary database and will run the restore on it. The cycle will repeat in reverse
the next time around. The setup seems fairly straight forward and will not require any down time. I am looking for feedback and if anyone has attempted something similar before?
↧