Best Approach for Shadowing a Database on Same Instance

  • I am being asked to create a copy of one of our production databases on the same instance. This copy will be used for reporting and end users will be pointed to it rather than the production database. This "shadow" database will be kept read only to the end users and is the primary reason to point them to the copy rather than the original. What is the best approach to keep this database up to date to within maybe 15 minutes or an hour of production database changes? Mirroring? Log Shipping? Replication? Database Snapshot? I would like your thoughts.



    Del Lee

  • My preferred approach is transactional replication to offload your reporting reqs. Usually I then create an AD group with read permissions on the replicated database for them to "query" from SSMS or Report builder.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply