Known features not yet supported
This functionality is not yet supported in comparison, export and sync. You should take care of it yourself. High severity issues usually require manual editing of the sync script, while lower severity issues can often be handled in preparatory or final scripts.
|1||4||Objects WITH ENCRYPTION||When an object is created WITH the ENCRYPTION option, the original object statement cannot be obtained from any catalog views (sys.sql_modules). In this case, AutosyncDB uses a throw stub as a legitimate object statement instead of the original one, which allows it to continue working with such databases. However, you should then take care of comparing, creating and re-creating such objects yourself.|
|2||5||Table columns MASKED WITH FUNCTION (Dynamic Data Masking)|
|6||5||SQL Graph Architecture objects|
|7||3||Service Broker Architecture objects|
|8||3||Extended Stored Procedures|
|9||2||User STATISTICS objects|
|10||5||Security Policy objects|
|11||5||System-Versioned Temporal tables|
|12||5||Table columns ENCRYPTED WITH (Always Encrypted Tech)|
|13||5||Tables as FileTables|
|14||5||Table LOB storage space location (TEXTIMAGE_ON)|
|15||5||Tables as FILESTREAM data storage (FILESTREAM_ON)|
|16||4||LOCK_ESCALATION table option|
|18||3||Database DDL triggers|
|20||1||Default and Rule objects|
|21||4||Default and Rule objects (in use)|
Not sure yet?
If you have some doubts about specific features, you can run some tests by comparing a database with such features to itself and then to a clean database. The answers to these questions will help you make a decision: Does AutosyncDB show these features correctly in the Differences view? Is the comparison correct? Is the sync script correct?