Convert databases to a different type - Intergraph Smart 3D - Administration & Configuration - Hexagon

Intergraph Smart 3D Project Management

Language
English
Product
Intergraph Smart 3D
Subproduct
Project Management
Search by Category
Administration & Configuration
Smart 3D Version
13.1

You can convert a Smart 3D Microsoft SQL Server database to an Oracle database or convert a Smart 3D Oracle database to a Microsoft SQL Server database using the Configure Project Settings for Drawings Utility. The wizard is a stand-alone utility that runs independently of Project Management. The utility is delivered to the [Product Folder] \Core\Container\Bin\Assemblies\Release folder as S3DDBConvertWizard.exe.

The utility supports these database conversions:

  • Site and site schema from SQL Server to Oracle or from Oracle to SQL Server.

  • Catalogs and catalog schemas from SQL Server to Oracle or from Oracle to SQL Server.

  • Models from SQL Server to Oracle or from Oracle to SQL Server.

The database conversion process generates two log files in the Temp folder:

  • ConvertDBStatus.log shows source and target database details, conversion status, and validation of converted databases. This file indicates whether there is any mismatch in the count of rows in the source and target databases.

  • ConvertDBError.log shows conversion errors, if any exist.

  • You must run the Database > Integrity Command and clean all corrupted objects that are of fatal or crucial severity before running database conversion on a source database.

  • You can convert all Smart 3D databases at the same time. However, if you choose to convert databases separately, the databases must be converted in the following order:

    1. Site and site schema

    2. Catalogs and catalog schemas

    3. Models

  • All users must be logged out of the source databases. No one can access or change the source databases during the conversion process.

Limitations

When converting databases, you must be aware of the following limitations:

  • This utility supports only non-replicated databases. The replicated databases must be consolidated before conversion.

  • If you are converting a SQL Server database to Oracle, the name of the target Oracle database must not exceed 30 characters or start with a numeric character.

  • If you are converting a SQL Server database to Oracle, Oracle database table names, view names, and column names must not exceed 30 characters or start with a numeric character. If any table name or column name exceeds 30 characters or starts with a numeric character, the software logs a warning message in the conversion log file.

  • Reports under a drawing snap-in that have parametric inputs (asking filters) must be redefined.

  • Custom reports have to be written to support both SQL Server and Oracle SQL query statements. SQL query statements written only to work for SQL Server must be rewritten to work with Oracle. Likewise, Oracle query statements written only to work with Oracle must be rewritten to work with SQL.

  • If a table only contains data created by a data-validation task, such as Database Integrity or Verify Consistency Report, then such tables are not converted. You must run these tasks again on the converted databases to get the latest information. All batch jobs that were created before conversion must be recreated after conversion.

What do you want to do?