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 |
|
coolerbob
Aged Yak Warrior
841 Posts |
 Posted - 2005-05-04 : 06:26:01
|
Most our users are often in browse mode. They want to see all kinds of complex summaries and stats rolled up before they may go in and browse specifics or start editing.What I have in mind is to have two databases: The OLTP DB and the DSS (Decision-support) DB. So they would see data from the DSS DB before they might go and edit the OLTP DB.What is the best strategy to move data continuosly from OLTP to DSS? Merge Replication? Triggers?What approach do I take for the DSS: -
Store calculated values in the DSS DB (maybe updated from triggers in the OLTP DB-
Use Views on the OLTP DB and replicate them to tables in the DSS DB (I can see performance problems here)-
Replicate the data in it's complete form with merge replication and then use OLAP-
My concern with continuous live merge/transactional replication is the demand on the transaction log. Is that a worthy concern?Does anyone have any experience in trying any of these methods? Or know which way (or some other way) will be the best bet? |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-05-04 : 07:05:22
|
transactional replication where changes are done at the OLTP DB side,the DSS DB serves as reporting server  if you are worried about transactional log getting full, create routine maintenance or set the log to simple recovery  --------------------keeping it simple... |
 |
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-05-04 : 07:36:53
|
| Ok, fab. And how would you summarize data so that users can see it quickly as they flick through entities? OLAP? |
|
|
|
|
|
|
Good case for replication?