Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
thakor
Starting Member
1 Post |
 Posted - 2011-04-07 : 02:46:14
|
| Hello,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 databasesorB] 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.TomasTomas |
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2011-04-07 : 14:50:38
|
| if both databases are on same instance you may not see much performance improvement from splitting the data into 2 databases.. on the contrary you may end up hurting performance with distributed queries.. If you are going to separate them onto 2 instances, do you need near-realtime data on History? or does periodic restores (perhaps once a day or twice a day) work? Also the size of your databases and production workload may affect the decision one way or another..Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
 |
|
|
|
|
|
Replication consideration