Setting up a History slave

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:

  1. 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.
  2. 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

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