Schema verification after refresh
After refreshing metadata in the previous step, SQL Tran now has an accurate, up-to-date understanding of the objects in both the source and target staging databases. During the refresh, SQL Tran queried both environments to update its internal model of the project’s schema, including object existence, dependencies, and lifecycle status.
In this section, we’ll revisit the Workspace screen and examine how this refreshed state is reflected in the schema lifecycle indicators for our example project.
1. Go to the Workspace screen
Click the Workspace icon in the left-hand sidebar to switch to the Workspace screen.
2. Select the Objects tab
Make sure the Objects tab on the left side is selected. This displays a structured tree view of all database objects included in your project.
3. Expand an object category
Database objects are grouped into logical categories such as Types, Tables, Views, Procedures, and Functions.
Click any category to reveal its associated objects.
4. Choose a database object
Select any object from the expanded list to open it in the editor and view its lifecycle metadata.
5. Inspecting the Creation stage indicators
Inspect the object's lifecycle indicators in the header pane, with a focus on the Creation stage. You can use your browser’s zoom feature if needed to view the details more clearly.
The Creation stage is visualized with two adjacent circular indicators. The left indicator shows whether the object exists in the source staging database, while the right indicator reflects its presence in the target staging database. If an indicator appears as a small empty circle, it means the object is missing from that environment. A larger shaded circle with a checkmark signifies that the object does exist.
Earlier in this training, SQL Tran showed that the object existed only in the target staging database because the metadata had not yet been refreshed. Now, after refreshing metadata, both circles are correctly filled, indicating the object exists in both environments.
You can also hover over the Creation stage in the header pane to display a tooltip confirming the object’s presence in the source and target databases.
6. Check lifecycle indicators in the Objects tree
To the left of each object in the Objects tree are four small circular status indicators. The third indicator corresponds to the Creation stage and is displayed as a split circle. The left half of this split circle shows whether the object exists in the source staging database, while the right half indicates whether it exists in the target staging database.
In our example, both halves are filled, meaning the object exists in both databases.
You may also hover over the object to see a detailed tooltip that includes the object’s name and the status of each lifecycle stage. For the Creation stage, status is shown as two entries: Exist in source: YES/NO and Exist in target: YES/NO. This clearly indicates whether the object is present in each staging environment, and in our case confirms that it now exists in both.
7. Creating the source staging schema
In our demo project, the source staging database was pre-populated with the project’s schema. However, SQL Tran was unaware of this until metadata was refreshed. That’s why, initially, SQL Tran displayed the source staging indicators as empty.
In typical scenarios, neither the source nor the target staging database contains any project objects at the start. In such cases, SQL Tran allows you to populate either environment by creating the full schema using the Actions menu.
To create the schema in the source staging database, follow these steps:
Go to the
Overviewscreen.Open the
Actionsmenu.Expand the
Source staging databasesection.Select
Fully recreate all objects.
This operation will drop and then create all objects from the current project in the source staging environment. It follows the same process previously used to create the schema in the target staging database.
(For more information, see the following page: Creating the target staging schema.)
Last updated