Set Up a SmartPlant Instrumentation Database 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 paths you specify in this procedure refer to the database server local folders (non-network folders).  Do not use network drives or network server names in the paths.

  1. On your Windows Start menu, navigate to the Intergraph SmartPlant Instrumentation program icons and click DB Setup Utility.

  2. On the Microsoft SQL Server Connection dialog box, under Server name, do one of the following:

    • Accept the server name (or the instance name if the instance is not the default instance) that the software retrieves from the Intools.ini file, created during SmartPlant Instrumentation installation.

    • Type the required name of the target database server machine or another named instance to which you want to connect for the SmartPlant Instrumentation database setup.

  3. Under System Administrator logon password, type the appropriate password if required or leave this field empty if the password is not required.

  4. Click Connect to connect to the SQL Server database on your server machine and open the Target Database Parameters dialog box, where you can set parameters for the target SmartPlant Instrumentation database and start the database setup process.

    If you changed the Server name setting, when you click Connect, in the [Database] section of the Intools.ini file, the software changes the ServerName parameter, and also updates the Server parameter in the current SQL Server ODBC profile.

  5. Under Target database name, type the name of the SmartPlant Instrumentation database for which you want to run the setup process.

    SHARED Tip The SmartPlant Instrumentation database name must be unique within your SQL Server that you specified on the Microsoft SQL Server Connection dialog box.

  6. Under Admin schema, accept the default Admin schema logon name SPI_DBAMN or modify the name as you require, provided that you type a setting that is different from the Admin schema logon password.

    • The logon name can only start with a letter and may not contain spaces.  You can use an underscore (_) to indicate a space.

    • If this is the first database setup session for SmartPlant Instrumentation 2009 in the current SQL Server database, the logon name must be unique in the SQL Server database server.

    • If this is not the first database setup session, you can use an existing Admin schema logon name but in this case, you must also use the existing Admin schema logon password.  You can only use an existing Admin schema logon name if the password in that Admin schema is different.  For example, if in another SmartPlant Instrumentation database, the Admin schema logon name is IN_DBAMN, and the password is also IN_DBAMN, you cannot use IN_DBAMN for the Admin schema in the new SmartPlant Instrumentation database.

    • If you want to define a new logon name, you must also define a new logon password, different from the logon name.

  7. Accept the default Admin schema logon password SPI_DBA or modify the password as you require, provided that you type a setting that is different from the Admin schema logon name.

    • The logon password can only start with a letter and may not contain spaces.  You can use an underscore ( _ ) to indicate a space.  If you want to encrypt the password, see Encrypt the Admin Schema Logon Password (see ).

    • If this is the first database setup session for SmartPlant Instrumentation 2009 in the current SQL Server database, the logon password must be unique in the SQL Server database server.

    • If this is not the first database setup session, you can either use the existing Admin schema logon password or type a new password.  If you want to use the existing password, you must also use the existing logon name.  If you want to define a new password, you must also define a new logon name.

    • The software automatically converts all the password characters to upper case.  This means that after completing the database setup, if you need to connect to the SmartPlant Instrumentation database externally, you must enter the Admin schema logon password using upper-case characters.

  8. In the subsequent boxes, accept the default parameters or modify them as needed.

    • If you change the default file size definitions, make sure the total file size that you specify does not exceed the available empty space on your selected disks.  The default is 70 MB, which includes the size of the file for the recommended initial size of the Admin data and indexes, and SmartPlant Instrumentation database log file.

    • Each of the file names must be a legal name.

    • Each file name must be unique within your database.  Special characters are not supported.

  9. Click OK and make sure the database setup process is completed successfully.

  • If the database setup process is not successful, you cannot use the SmartPlant Instrumentation database and must manually clean up the SQL Server database before running the DB Setup Utility again.  For details, see Clean Up the SQL Server Database.

  • On SQL Server 2014, the DB Setup Utility automatically clears the Enforce password policy check box for each SmartPlant Instrumentation schema login created in the instance.  If your company policy requires that this check box is selected, after completing the database setup, select the Enforce password policy check box for each of the SmartPlant Instrumentation logins, that is: SPIsuper and SPI_login, which are created automatically and shared for all SmartPlant Instrumentation databases, and Admin schema login, whose name you defined during the current database setup.  You will have to select the Enforce password policy check box every time you create other logins for SmartPlant Instrumentation schemas.  The Domain schema and View-Only Domain schema logins are created when initializing a domain; the As-Built schema login — when creating an owner operator domain; the Project and Combined Project schema logins — when creating a project.  For details about database schemas, in the SmartPlant Instrumentation Configuration and Maintenance Guide, see SmartPlant Instrumentation Database Technical Review > Logon Data and Database Connection Security > SmartPlant Instrumentation Database Schemas.