Best solution for reporting database

Posted by zzyzx on Stack Overflow See other posts from Stack Overflow or by zzyzx
Published on 2010-04-29T06:42:35Z Indexed on 2010/04/29 6:47 UTC
Read the original article Hit count: 349

Here is the situation: There is a transaction intensive database - used for both routine transactions and reports.

I was wondering if I could isolate these two operations and 2 independent databases, so reports could run off of one database and all the transactions could occur in another one. This would improve performance for the OLTP SQL database.

I have gone over a few options like, Mirroring, Log shipping, Replication, Snapshots, Clustering - but would like to discuss the best possible strategy for the desired result.

Please advise the best solution to implement this strategy, or any other thoughts/suggestion you may have.

© Stack Overflow or respective owner

Related posts about sql-server

Related posts about reporting