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

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.

In sqlServer you can use this script to find where you have the most rows in your historyserver - this may be a good indicator if you need thinning: