Synchronizes a target database with the package.
The Sync step compares the database schema and data with the source package, identifies differences, and applies the necessary changes to bring the target database up to date.
1. On the Configure page, select Build Steps.
2. Click Add build step, then select dbForge DevOps Automation for SQL Server – Sync a database package.

3. Under Database package to sync, specify the package ID.
4. Under Target database, specify the server and target database to be updated, and the authentication method.

5. Click Save.
The table provides a list of settings you can customize for the Sync step.
| Name | Description |
|---|---|
| Package ID | Specify the ID of the package you want to use to update the target database. This ID must match the one specified in the Build step. |
| Server | Specify the target server name. |
| Database | Specify the target database name. |
| Authentication method | Select Windows Authentication or SQL Server Authentication. If you select SQL Server Authentication, specify the username and password that you use to connect to the server. |
| Schema Compare filter | Note: You can filter data by using a filter file (.scflt) that defines the filtering rules. After generating the file, add it to your version control system (VCS) so it can be used in the CI process. |
| Transaction isolation level | Select the transaction isolation level. The available options are:
|
Note
The Sync step doesn’t support running a comparison on its own. Whenever you execute it, it automatically initiates synchronization between the source and target databases. To obtain a comparison report without synchronization, use the dbForge Studio for SQL Server Enterprise or Professional edition command line instead without using the
/syncswitch. For example:"C:\Program Files\Devart\dbForge Studio for SQL Server\dbforgesql.com" /schemacompare /source connection:"Data Source=<server_name>;Initial Catalog=A1;Integrated Security=False;User ID=<user_name>" /target connection:"Data Source=<server_name>;Initial Catalog=A2;Integrated Security=False;User ID=<user_name>" /report:D:\report.xml /reportformat:xmlIf you need a customized solution in your DevOps pipeline, the dbForge Studio command-line interface provides a flexible option that can be adapted to your specific requirements. This approach allows you to configure commands for your particular steps and run the tool with the necessary options and parameters.