Page History
After reviewing the schema compare results, select objects for synchronization, then click click
and complete the synchronization process in the following order.
...
The Review Dependencies tab shows objects selected for deployment and the dependent objects. The dependent objects are synchronized to prevent the deployment script from failing. Objects are displayed in the Affected Objects column because these objects are referred by or refer to the objects in the Referencing Or Referenced By column. When you click a dependent object, you can view the differences between both the source and target objects in the default viewer.
If a dependent object supported in Aqua Data Studio is not supported in Schema Compare, then during deployment, Schema Synchronization will not include dependencies of this dependent object, and the deployment script will fail. To synchronize these dependencies, create the dependent object on the target server before executing the deployment script.
From the Dependent Objects area, you can include/exclude dependent objects for synchronization. However, you cannot unselect the dependent objects that are also present in the Objects Selected For Deployment area.
We recommend deploying all dependent objects, to avoid deployment script from failing or receiving unexpected results.
You can use Search to narrow down the result. You can also copy the list of dependent objects to a different editor.
...
You can prevent data loss from the target column by mapping the target column to the correct source column.
In the Target Table Column Mapping pane, the columns are automatically mapped to Source Columns based upon data type or other attributes that are compatible with the target column. You can retain this default selection or choose a different column from the drop-down list.
To map the target column to a different column in the drop-down list, select the target column, and then from the adjacent Source Column drop-down list, choose a column to map.
Schema Synchronization will generate a Column renamed warning in the Warnings tab. This warning means Schema Synchronization will rename the target column to the source column.
When you execute the deployment script, Schema Synchronization renames the target column name to match the source column name. 
Drop Column from the Target Table
From the Source Column, if you drop the target column then Schema Synchronization will generate a Column dropped warning, which means, Schema Synchronization will drop the column from the target table.
When you execute the deployment script, Schema Synchronization drops that column from the target table.
...
Schema Synchronization will show you this tab only if it finds issues that might require user input.
This table shows the severity for each warning that can affect the deployment script and the action you can take to resolve them.
...
- If the target column contains more data than the source column, then data truncation might happen from the target column.
- If the issue was ignored, then the possibility of deployment script failure and data loss from the target column will be high because schema synchronization will execute the script with the column name instead of the conversion function.
- If data of the target column is not in the correct format, then the deployment script will fail, and data loss from the target column will occur.
Data type must be converted in this column
...
- If the issue was ignored, then the possibility of deployment script failure and data loss from the target column will be high because Schema Synchronization will execute the script with the column name instead of the conversion function.
- If data of the target column is not in the correct format, then the deployment script will fail, and data loss from the target column will occur.
No value specified for a NOT NULL column
...
If you choose the Ignore issue option, Schema Synchronization will add NOT NULL for the target column and will add no value for this column in the deployment script and will display a No value specified for a NOT NULL column warning in the Warnings tab. This warning means no value is specified for the NOT NULL column.
When you execute the deployment script, the deployment script will fail only if the NULL column in the target database contains a NULL value. 
Constant value must be assigned in this column
...
If you choose the Ignore issue option, Schema Synchronization will add the constant value of a data type in the deployment script defined by Schema Synchronization itself and will display a Constant value will be assigned warning in the Warnings tab. This warning means the constant value of a data type will be added in the deployment script.
For both the above actions, when you execute the deployment script, data in the target column will be lost. 
Arithmetic overflow can occur
...
- If the target column contains more data than the source column, then data loss from the target column might occur.
- If the issue was ignored, then the possibility of deployment script failure and data loss from the target column will be high because Schema Synchronization will execute the script with the column name instead of the conversion function.
Grant Issues
Grants for missing role cannot be deployed
...
If you execute the deployment script without creating the missing role in the target database, the deployment script will fail.
Grants for missing user cannot be deployed
...
If you execute the deployment script without creating the missing user in the target database, the deployment script will fail.
Grants on missing grantees cannot be deployed
...
If you execute the deployment script without creating the missing grantee in the target database, the deployment script will fail.
Grants for missing group cannot be deployed
...
If you execute the deployment script without creating the missing group in the target database, the deployment script will fail.
Options
Schema Synchronization will display various options that you can include or exclude from the deployment script.
...