Schema Analysis

The Schema Analysis page shows the analysis for a given schema only, instead of for the whole source.

Using the Schema Analysis page can help understand the complexity of migrating a single schema rather than the whole database. This information can also help understand the relative complexity of certain schemas vs. the rest within the source.

This level of analysis is only available for Oracle and PostgreSQL sources.

The page contains the following subsections:

1. Overview

2. Details

3. Features

4. Workload

5. Programmatic Objects

6. Schema Dependencies

Analysis Behavior

The Overview, Features, and Workload sections behave the same as their counterparts in the full source analysis page, except that the data they consider is only from the current schema of this page. Score calculation and other findings aggregate the values found in this schema alone, or which are allocated to this schema. Changes to the target on this page cause re-calculation of the various elements with respect to that source but do not affect the overall score for the parent full source.

The Details section reflects source-wide information.

The Programmatic Objects and Schema Dependencies sections both reflect information specific to the current schema only. They have no counterpart on the parent source page.

Programmatic Objects

Programmatic objects are database objects that contain code or script. These include custom stored procedures, functions, and trigger definitions.

Using this section helps understand the volume of code which is embedded in the source database. This in turn can help drive effort or complexity estimates.

This section lists the objects detected, the schema they were found in, and the estimated lines of code each one contains. The estimate for the lines of code measure is based on a naive line count of the object’s source expressed as text.

Schema Dependencies

The Schema Dependencies section shows detected dependencies between the current schema and other schemas in the source. The dependency relationship is determined by the set of permissions given to the schema owner on other schemas.

Using this dependency can help understand the degree of isolation of the current schema. Detected relationships indicate that migration of this schema alone in isolation may incur extra complexity.

The dependencies are all direct dependencies. The current schema is the center of the graph, with potential dependency relationships to other schemas as nodes. Since permissions are granted to the owner, no further transitive relationships are implied.