Documentation:Setting up a History slave: Difference between revisions

Setting up a History slave

Revision as of 14:34, 8 April 2021

Read here on why you want a History slave server - Purpose of History Server

Recent changes makes it possible to use SQLCompact to test the MDriven History server - but you will most likely need more space than what SQL compact can handle.

Steps:

On the main MDrivenServer:
1. Ensure MDrivenServerSynk
2. Switch from "Normal" to "Master"
3. Copy/backup the database from the master - restore it in second MDrivenServer.
In Second MDrivenServer change mode to "History Slave"
1. In History Slave ensure Version compatible
2. In History point out the master MDrivenServer and set user and pwd for master.

Test by making changes towards Master - within short changes show up in History slave

Thinning and truncating a History server

On classes set tagged value NoHistory=true to make HistoryServer skip this class for versioning. This may be desirable when having fast moving reference data you do not own - like daily imports from other systems that you do not deem important enough to track.

This page was edited 98 days ago on 02/10/2024. What links here

@@ Line 12: / Line 12: @@
 ## In History point out the master MDrivenServer and set user and pwd for master.
 Test by making changes towards Master - within short changes show up in History slave
+==== Thinning and truncating a History server ====
+On classes set tagged value NoHistory=true to make HistoryServer skip this class for versioning. This may be desirable when having fast moving reference data you do not own - like daily imports from other systems that you do not deem important enough to track.