Using the Reports screen

The Reports screen in SQL Tran provides a centralized location for analyzing and reviewing project-wide reports that offer valuable insights into translation issues, complexity metrics, testing estimates, billing events, and more. These reports are updated in real time as the source database is analyzed and translated.

Each report is presented as a visual panel containing a title and a brief description, allowing users to quickly understand the purpose of each report. Clicking a panel opens a detailed view of that specific report.

The following reports are available:

• Objects with errors

• Grouped errors

• Objects could not be created

• Objects complexity

• Objects referenced by

• Objects depending on

• Translation Person-days summary

• Testing Person-days summary

• Billing events

Together, these reports provide multiple perspectives on the project’s translation status, completeness, and automation effectiveness.

A more detailed breakdown of each report follows.

Objects with errors

This report lists all database objects that contain translation errors.

Each object is displayed with its type icon and name. Clicking an object opens the Workspace screen and displays its SQL, allowing for immediate inspection and resolution.

Below each object, all associated error types are listed in a single line, separated by commas.

For example (icons below symbolically represent object types and differ from the actual icons used in the interface):

⋔ dbo.TestUnsupportedSystemObjects
└── FOR BROWSE/XML/JSON, RECURSIVE QUERY, $PARTITION

▦ HumanResources.Employee
└── ORGANIZATIONNODE.GETLEVEL

👁 Person.vAdditionalContactInfo
└── XML METHODS

Use the filtering pane on the left to narrow the view to a specific object type. The available filters are:

• All – Displays all database objects.

• Procedures – Displays only stored procedures.

• Functions – Displays only functions.

• Tables – Displays only tables.

• Views – Displays only views.

Grouped errors

This report organizes all translation errors detected in the project by error type.

For each error entry, a list of all affected objects is shown underneath. The number of occurrences for each error type is displayed to the right of the error label, aligned with dot leaders for readability.

Each object is listed with its type icon and name. Upon clicking an object, the Workspace screen displays its SQL for further analysis and edits.

For example (icons below symbolically represent object types and differ from the actual icons used in the interface):

XML METHODS ...................... 3
└── 👁 HumanResources.vJobCandidate
└── 👁 Person.vAdditionalContactInfo
└── 👁 Sales.vPersonDemographics

ORGANIZATIONNODE.GETLEVEL ........ 1
└── ▦ HumanResources.Employee

This view supports prioritization by surfacing the most frequently encountered translation issues.

Objects could not be created

This report lists all database objects that failed during the creation step in the target staging database.

These failures often indicate compatibility issues or other problems that require attention and should be resolved before production deployment.

When an object in the list is clicked, it is opened in the Workspace screen with its SQL ready for review and troubleshooting.

In this example project, no objects failed during creation in the target staging database, so the report appears empty.

Objects complexity

This report provides a detailed tabular view of all database objects and their calculated complexity levels.

It complements the Complexity of objects histogram and Most complex objects pane in the Overview screen by offering a filterable breakdown of object complexity and structural metrics, as determined by SQL Tran’s semantic SQL engine.

Each row in the table represents a single object and includes the following columns:

• Object – Displays the type icon and object name, sorted alphabetically.

• Complexity level – Assigned complexity grade on SQL Tran’s six-point scale.

• Nodes – Number of semantic SQL language elements present in the object.

• Statements – Total number of SQL statements.

• LoC – Total lines of code in the object’s SQL.

Each object can be clicked to load its SQL into the Workspace screen for code evaluation and optimization.

On the left, a filtering pane provides type-specific views of the data. Filters include:

• All – Displays all database objects.

• Types – Displays only types.

• Tables – Displays only tables.

• Procedures – Displays only stored procedures.

• Functions – Displays only functions.

• Views – Displays only views.

Objects referenced by

This report displays an alphabetical list of all objects referenced by other database objects.

For each referenced object, its dependents are shown in a tree structure beneath it.

All objects are displayed with a type icon and a name, making it easy to distinguish between object types. Clicking any object opens the Workspace screen with its SQL loaded, allowing further inspection and analysis.

For example (icons below symbolically represent object types and differ from the actual icons used in the interface):

▦ Production.ProductModel
└── 👁 Production.vProductAndDescription
└── 👁 Production.vProductModelInstructions
└── 👁 Production.vProductModelCatalogDescription

▦ Sales.SalesOrderHeader
└── 👁 Sales.vSalesPersonSalesByFiscalYears

Use the filtering pane on the left to limit the view to specific object types. The available filters are:

• All - Displays all types of database objects.

• Types - Displays only types.

• Tables - Displays only tables.

• Functions - Displays only functions.

• Procedures - Displays only stored procedures.

• Views - Displays only views.

This report is particularly useful for tracing usage patterns and understanding downstream dependencies across the codebase.

Objects depending on

This report presents an alphabetical list of database objects along with the other objects they depend on.

Each object is shown with its dependencies structured hierarchically beneath it.

Type icons and object names are shown for all objects, helping differentiate between object types. Once an object is clicked, its SQL appears in the Workspace screen ready for closer examination.

For example (icons below symbolically represent object types and differ from the actual icons used in the interface):

👁 Production.vProductAndDescription
└── ▦ Production.Product
└── ▦ Production.ProductModel
└── ▦ Production.ProductModelProductDescriptionCulture
└── ▦ Production.ProductDescription

👁 Sales.vStoreWithDemographics
└── ▦ Sales.Store

To focus on particular object types, use the filtering pane on the left. It provides the following filters:

• All - Displays all types of database objects.

• Procedures - Displays only stored procedures.

• Functions - Displays only functions.

• Tables - Displays only tables.

• Views - Displays only views.

This report helps uncover upstream dependencies and analyze what each object relies on to function correctly.

Translation Person-days summary

This report provides a detailed tabular view of all database objects, estimating the manual effort required to translate them and highlighting the time saved through SQL Tran’s automation.

Each object appears as a row in the table, with these columns:

• Object – Displays the type icon and object name, sorted alphabetically.

• LoC – Total lines of code in the object’s SQL.

• Total days – Estimated manual translation effort, expressed in person-days.

• Saved by SQL Tran – Approximate time savings achieved through automated translation.

• Requires manual translation – Remaining effort that still requires manual work.

Clicking an object opens its SQL in the Workspace screen for review and any necessary follow-up actions.

A filtering pane on the left allows narrowing the view to specific object types. Available filters include:

• All - Displays all types of database objects.

• Types - Displays only types.

• Tables - Displays only tables.

• Procedures - Displays only stored procedures.

• Functions - Displays only functions.

• Views - Displays only views.

This report is especially useful for effort estimation, prioritization, and tracking translation productivity across the codebase.

Testing Person-days summary

This report estimates the manual effort required to test each database object, alongside the time saved through SQL Tran’s automation.

The data is presented in a table, where each row corresponds to a single object. The following testing-related metrics are shown in separate columns:

• Object – Displays the type icon and object name, sorted alphabetically.

• Complexity level – Assigned complexity grade based on SQL Tran’s six-point scale.

• Hours – Estimated manual testing effort, expressed in hours.

• Saved by SQL Tran – Approximate time savings achieved through automation.

• Requires manual translation – Remaining effort that still requires manual testing.

When an object is clicked, its SQL is displayed in the Workspace screen for closer analysis.

To control which object types are shown, use the filtering pane on the left. Available filter categories include:

• All - Displays all types of database objects.

• Types - Displays only types.

• Tables - Displays only tables.

• Procedures - Displays only stored procedures.

• Functions - Displays only functions.

• Views - Displays only views.

This report offers a consolidated view of testing requirements across the entire project, helping users identify areas that may require further validation.

Billing events

This report displays all billing-related actions and object-level charges associated with the current project.

Billing events are listed in chronological order, each presented as a block containing a summary header followed by the list of affected database objects.

Each billing event header includes the following details:

• Event source – Action triggering the event.

• Event date – When the event occurred.

• Affected objects – Number of objects involved.

The participating objects are listed beneath the header, grouped by complexity level. Each object is shown with its type icon and name to clearly distinguish its role and type.

(Note: For projects using the SQL Tran BYOL (Bring Your Own License) plan, no actual charges apply. However, billing events are still recorded for transparency and auditing purposes, and the report remains available for informational use.)