We want to use MirrorSync to synchronise a very large FileMaker database to a SQL Database.
The Hub (FileMaker) Database controlls our production and should contain only data from the last 2 years.
The Spoke (SQL) Database is used by BI-Department to analyse actual and historical data and must contain alltime data
The direction of the sync is one-way from hub to spoke.
On a certain date all data older than 2 years is deleted (really deleted - not just marked as deleted!!!) from the hub. I'm wondering how can I prevent MirrorSync from syncing these deletetions to the spoke?
One solution would be to clear or extend the primary keys in the spoke. This would work, because the primarykeys were created only for MirrorSync. But it's not a nice solution. I would prefer a seperate field "locked" in all tables that marks these records as locked. Is there any customization option that let me exclude records where locked=1 from being deleted by MirrorSync?
Thanks in advance for any ideas on this topic.
Best,
Markus