Reports about the scanned sources can be exported and used for arbitrary offline purposes.
Exporting is performed by clicking on the EXPORT button at the top of the page. Once clicked, a downloadable spreadsheet containing the information of all currently filtered sources is created.
Exported reports include all currently filtered sources. Each DB engine has its own report format. All filtered sources of a DB engine are included in that DB engine report. In cases when sources are of multiple DB engines, the export function generates separate reports, one for each DB engine.
Once the reports are ready, the browser starts downloading them.
The report header includes information about the time and date on which the report was generated, as well as the source-target pair selected for the analysis.
Your migVisor license determines the depth and scope of information included in the report. The report header will indicate if any information was omitted due to licensing.
In case you need any further clarifications, please refer to migVisor Support.
The report is exported as an Excel spreadsheet. It comprises all the source objects found by the scan including tables, functions, indexes, features, migration insights, etc., together with their impact on the migration complexity.
Report Content for Oracle, SQL Server, PostgreSQL, and MySQL
The report format for Oracle, SQL Server, PostgreSQL, and MySQL share the same format and spreadsheet tab structure.
The tab content in an RDBMS report is as follows:
General summary on the the discovered databases, their migration complexity score, and migration complexity level.
In the Servers column, the hostnames are clickable. Click a server name to move to a corresponding hostname tab to see details of a particular database (see the description of the #Database name tab below).
Schemas found in the discovered databases and their migration scores.
Alternative cloud platforms available for migration and complexity levels for each selected database to migrate thereon. Depend on the basic source and target selection.
Summary on the features found in all the discovered databases. Includes features IDs, names and descriptions.
Excluded features are not shown in the features list.
Shows applications connected to the database(s). For details refer to Applications Management.
Key findings in the source which are useful in determining sizing for the target. For details refer to Source Target Sizing.
For Oracle, SQL Server, PostgreSQL, and MySQL only.
Workload information is specific for Oracle databases. For details refer to Source Workload (Oracle, SQL Server, PostgreSQL, MySQL).
For Oracle only.
Average complexity of the queries executed on the source. It depends on the Query Execution Plan - a number of steps needed to fulfill the query. The higher the number of steps, the higher the workload complexity.
Total number of features found in the database(s). For details, see Source Features.
Excluded features are not included into the total count.
Lists of features found in each discovered database and their migration scores. Split by database hostnames.
Report Content for MongoDB
The spreadsheet tab structure for MongoDB is unique to MongoDB due to its unique characteristics and various cluster deployment topologies.
The tab content in the MongoDB report is as follows:
General summary on the discovered clusters, their migration complexity score and migration complexity level.
In the Clusters Name column, the clusters names are clickable. Click a cluster name to move to a corresponding tab to see details of a particular cluster (see the description of the Cluster name tab below).
Topology types of the discovered clusters and their migration scores..
Summary on the features found in all the discovered clusters. Includes features IDs, names and descriptions.
Excluded features are not shown in the features list.
Key findings in the source which are useful in determining sizing for the target. For details, see Source Target Sizing.
Shows applications connected to the cluster(s). For details, see Applications Management .
Features lists split by clusters topology - standalone, replica set, sharded - and their migration scores.
Report Content for HBase
The spreadsheet tab structure for HBase is unique to HBase due to its unique cluster topology and column-store-oriented data storage.
The tab content in the HBase report is as follows:
General summary on the scanned HBase databases, their zookeeper quorum address, and storage usage.
The cluster id in the Clusters ID is clickable. Clicking the id navigates to the corresponding cluster’s tab.
Information about the hosts and nodes that HBase is running on. This includes HMaster and RegionServer hosts. It does not include replication targets, Zookeeper, or Hadoop participants (unless the host is shared with the HBase components). The tab breaks down store file counts, store file size and uncompressed store file size.
The logical layout contains a row for each column family. It includes table and column family settings.
Feature names, description, and occurence counts for the features detected in the scanned HBase.
Key findings in the source which are useful in determining sizing for the target.
The migration insights related to each cluster, along side their supporting values.
Key configuration entries retrieved during the scan.
For each HBase cluster in the report, there is a dedicated tab for the cluster named after the cluster id.
The tab contains the features, their source hierarchy, and values for the cluster.