SQL Server Performance

Replication consideration

Discussion in 'SQL Server 2005 General Developer Questions' started by thakor, Apr 6, 2011.

  1. thakor New Member


    I have following task in front of me:

    We have Production database that holds data for processing and reporting. As the database is growing, we need to split the database to Production and History. We need to use both databases for reporting services.

    My question is, is it better

    A] to split the database into Production and History and build joins/unions accross databases


    B] copy all data to History, remove old data from Production and run reports only on the History database. Could be the copy operation made through replication? If so, how can I prevent replication of the clear operation?

    Could anybody help me with the decision making, please? Thanks a lot.
  2. satya Moderator

    Welcome to the forums.
    Basically you need an archiving solution where you can divert the reporting requirements from live database, which is a good decisions in terms of scalability.
    Do you need all the tables from Production database on History database?
    How many tables you require for reporting?
    How often the reporting/ad hoc queries are executed?

Share This Page