The sync comparison detects changes from the database side

[HansinVogado]

I'm using the database plug-in to export to a SQL Server database, but only from MY Archi-client, with no data changes (read-only to insert into your own datamarts for analysis and quality checks). However, time and time again, the synchronization comparison detects changes on the database side (which causes a synchronization on export). Worse still, after a few more exports, the Archi-model is corrupted and I have to restore a previous version from Git and truncate all the tables in the database.

Although I can see which data/views have been affected, I have no clue as to the cause. But I'm more interested in
(1) what could cause changes to the database in general (considering the fact that my database serves as a slave)
(2) An “export only” option, so that there is no synchronization; the differences between Archi-model and the database will only update the database.

I saw on the forum that someone else had the same problem, so I've just reproduced it here

[herve91]

Hi Hansin,
To be honest, there has been ages (about 1 year to be precise) that I haven't had time to work on my database plugin. Archi evolved and eventually, the version 3.2 of Archimate has been released.
Regarding your question, sometimes, the order of relationships or connections are changing, and in this situation, my plugin detects a change in the corresponding views. I never experienced components that are related as new (in Archi nor in the database) when it is not the case.
I'll try to conduct more tests.