SmartPlant Instrumentation Database Setup for SQL Server - Intergraph Smart Instrumentation - Installation & Upgrade - Hexagon PPM

SmartPlant Instrumentation Installation and Upgrade Guide

Language
English
Product
Intergraph Smart Instrumentation
Search by Category
Installation & Upgrade
Smart Instrumentation Version
2016 SP1 (11.0.1)

The DB Setup Utility creates an individual SmartPlant Instrumentation database in a SQL Server instance and enables you to configure this instance for working with SmartPlant Instrumentation.  You perform the database setup procedure after successfully installing the SQL Server database server, SQL Server client, and SmartPlant Instrumentation for SQL Server.

The DB Setup Utility performs the following operations (in the indicated order):

  1. Creates a SmartPlant Instrumentation database with SQL Server filegroups in the instance you installed on the SQL Server database server.

  2. Creates the INTOOLS_ENGINEER role and the following SmartPlant Instrumentation database schemas: SPIsuper, SPI_login, and Admin schema.

  3. Creates logon information (logins) at the instance level and associates the logon information with the SmartPlant Instrumentation database schemas.  For the SPIsuper and SPI_login schemas, the logins are created only once, during the first database setup.  These logins are shared for all the SmartPlant Instrumentation databases you create in this SQL Server instance.

  4. Creates database objects in the Admin schema of SmartPlant Instrumentation and fills these objects with data that appears in the IN_TEMPL template database, supplied with SmartPlant Instrumentation.

  • During the database setup, the INTOOLS_ENGINEER role receives system privileges and privileges for database objects included in the Admin schema.  These objects are shared for all domains you initialize.  When initializing a new domain, other database schemas of SmartPlant Instrumentation receive the INTOOLS_ENGINEER role.

  • If your SmartPlant Instrumentation database is created in an SQL Server named instance, make sure that in the [Database] section of the Intools.ini file the servername parameter value is as follows:

    servername=<Server Windows name>\<named instance>

    The following special characters cannot be used in passwords, database names, file names, and so forth:

    /

    \

    [

    ]

    =

    ;

    #

    :

    "

    !