Hi @mikelucito 

The process of migrating your existing Sync settings to an SQL Server database is very straightforward. However, before following the instructions outlined below it is important to confirm the version of Sync you are using. The instructions below apply to the v24 version of Sync which can be downloaded from the website. 

Starting with Sync 2024, the .NET edition of the application is deprecated. As a result in case you have a .NET version of Sync, you would need to migrate your current .NET edition of Sync to the Cross-Platform edition. Kindly check the following documentation for more details regarding migration to Java edition: https://community.cdata.com/how-to-with-cdata-72/migrating-cdata-sync-from-the-net-edition-to-the-cross-platform-edition-818 

Assuming you are using the latest version v24 of Sync, find the instructions for migrating the application database from the built-in database to an SQL Server database of your choice below:

1. The first step would be to export all your Sync settings by navigating to Settings -> Migration -> Export in Sync. This action will create a .zip file containing all your existing users, jobs, connections, etc.
2. In order to specify a database of your choice for saving the existing configurations in sync you would need to edit the sync.properties file. If you are not able to find it(sync.properties), you can generate it by running this command

   java -jar sync.jar -GenerateProperties

   in C:\Program Files\CData\CData Sync. You can read more about this here: https://cdn.cdata.com/help/ASJ/sync/Java-Edition.html#generating-the-syncproperties-file 
3. In the sync.properties file the app db is unspecified which means it is using a derby database by default. In order to save the app db in SQL Server you will need to specify a connection string for the SQL Server connection as follows:

   cdata.app.db=jdbc:cdata:sql:server=localhost;AuthScheme=Password;Port=54162;Database=NewDB;User=sa;Password=******;

4. After setting the connection string save the changes and make sure to restart the sync service. Once Sync is restarted, simply import the CDataSyncSettings.zip file and the existing configurations will be added to the new app db in SQL Server and you should be good to go.

In case you have an older .NET version of the Sync application and do not want to upgrade to v24 version for now, it will require different instructions. For this it would be best to reach out to our support team at [email protected] so they can further assist you.