Viewing the SQL differences
Published 21 August 2019
The lower (SQL Differences) pane displays a side-by-side listing of differences in the creation SQL script for an object. To display the SQL Differences pane, click an object in the upper (Results) pane.
You can adjust the height of the SQL Differences by dragging the blue bar up or down.
Clickto open the SQL Differences pane in a separate window.
Lines that contain differences are displayed with a shaded background; text within a line that is different is displayed with a darker shaded background.
The central column shows the type of difference:
this line of SQL will be added or changed if you deploy this object (the direction of the arrow indicates the database that will be updated)
this line of SQL will be removed if you deploy this object
There is no icon if the two lines are identical.
UseNext and Previous to go to lines that contain a difference. You can also use Alt + Up Arrow and Alt + Down Arrow.
The Line Differences bar
Clickand select Line Differences to display the Line Differences bar. The two versions of the line are shown one on top of the other. This is especially useful when the lines are too long to view all the text:
Colored blocks in the left scroll bar indicate the location in the script of lines that are different.
Searching and copying the creation script
To search the SQL statements, right-click, and click Find.
To search the SQL statements in the other data source, click Find on this side.
The search is not case-sensitive.
Viewing the object deployment script
To view the deployment script for the selected object, right-click in the SQL Differences pane, and then click View object deployment script.
The Single object deployment script dialog box is displayed.
You are recommended to deploy only using the full deployment script created by the deployment wizard, because the single objects script cannot account for dependencies. If you use the object deployment script to deploy a single object, there may be unexpected results, or the deployment may fail.
To view the full deployment script that will make the two databases identical, use the deployment wizard.