New/Edit Project Overview | SQL Delta Help

This page describes the common New/Edit Project workflow used across SQL Delta products. Most project editing behavior is shared and the editor is organized into tabs. The main differences are connection details, platform terminology, and a smaller number of engine-specific project options.

Common workflow

Choose the project type: Schema Compare, Data Compare, or Schema View. The project type changes the visible edit tabs and determines whether the project uses source and target connections or a single Schema View connection.
Use the Connection tab to define the source and target connections, or for Schema View define the single connection to inspect. Test the connection and then choose the database, schema context, or snapshot details needed for the project.
Work through the tabs that apply to the selected project type. Schema Compare and Data Compare use Map and Filter, Project Options, and On Completion. Schema View uses Schema Filter instead of Map and Filter. Data Compare also adds Table Selection.
Give the project a name and, if useful, assign it to a project group so it is easier to find again in Project Manager.
Save the project if you want to keep editing later. When you click Run, SQL Delta saves the current project first and then opens the run in a separate tab. If automatic project save is enabled, closing the edit tab can also save the project, and that auto-save can be turned off for the current edit session from the Auto Save indicator.

Where products differ

SQL Server: most of the existing screenshots and detailed connection examples align with SQL Server projects.
MySQL: projects are usually more database-centric and may require SSL or TLS configuration depending on the server.
Oracle: object ownership and schema language matter more, so shared pages that say schema often map more closely to owner context.

Use these detailed pages when the shared flow is not enough: