Using the Actions dropdown

In earlier steps, we used the Actions dropdown in the Workspace screen to perform several key operations such as overriding SQL, reverting changes, and ignoring specific objects. These options mirror the functionality available in the context menu that appears when right-clicking an object in the Objects tree.

In addition to those operations, the Actions dropdown also provides access to a range of testing-related actions. These additional capabilities operate on the currently selected database object and only become available once connections to the staging databases have been configured.

With both source and target staging databases now connected, we’ll explore these newly unlocked features in more detail.

Create object in source staging

This operation drops and recreates the selected object in the source staging database, ensuring that it is present in the source testing environment.

Create object in target staging

This operation drops and recreates the selected object in the target staging database, updating it to match the project’s current translated SQL definition.

Create object in target production

This operation attempts to drop and recreate the selected object in the target production database. For this to work, a connection to the production database must first be configured in Project settings.

In our demo project, this option is currently disabled, as no production connection has been set up.

Test generation operations

The Actions dropdown also provides test generation functionality for individual database objects:

• Generate Test – Attempts to create a single test for the selected object if conditions allow.

• Generate Multiple Tests – Attempts to create multiple test cases based on available data and static analysis.

If conditions are not met, SQL Tran displays a descriptive error message explaining why test generation was not possible.

These options are particularly useful for test-driven validation workflows. These and other test creation and management methods will be explored in detail on upcoming pages.

Actions dropdown summary

Now that staging database connections are active, many additional operations are unlocked in the Actions dropdown. Each action in the dropdown is context-sensitive, with its availability depending on several factors:

• The current lifecycle stage of the object

• Whether the required database connections are configured

• The object type and its translation status

All actions in this dropdown apply to the currently selected object in the Workspace screen.

With these operations now available and explained, we are ready to continue with the next topic in the training.