The system installs the HxGN EAM database by completing the following steps. You can also create and configure the database manually.
Only Microsoft SQL Server database administrators or equivalent should perform any function described in this chapter.
The system creates the directory you entered in the previous section, and then creates all of the scripts to the directory. Using Microsoft SQLCMD, the system executes the scripts created by the Installation Wizard, using the Microsoft SQLCMD utility. If you are creating and configuring the database manually, we recommend that you use the following syntax when executing the Microsoft SQLCMD utility:
sqlcmd |
-S ‘servername’ -d ‘databasename’ -U ‘userid’ -p ‘password’ -i ‘file name with path’ -o ‘log file name with path’ |
If you selected for the system to automatically run database scripts, the system runs the following scripts. If you select to run the scripts manually, you must manually run the scripts one at a time, in the given order listed below, as the system administrator user you created previously:
Script |
Function |
---|---|
createdb.sql |
Creates the database |
createuser.sql |
Creates the user and sets up the user privileges to access the database |
stxcreate.sql |
Creates the text system tables, which are used by 22sl120i.sql, 26sl120i.sql, and 40sd120i.sql |
10st120i.sql |
Creates the HxGN EAM table structure in the database |
stobjmasterdata.sql |
Creates master data to check table, view, and database objects. |
stxdata.sql |
Populates the text system tables with seed data from the test systems by using insert scripts |
stxdata1.sql |
Populates and updates the Microsoft SQL Server specific seed data Before running 22sl120i.sql, 26sl120i.sql, and 40sd120i.sql, run 7idef.sql to set up the session variables. To ensure that 7idef.sql, 22sl120i.sql, 26sl120i.sql, and 40sd120i.sql are all run during the same session, we recommend that you combine these four scripts into one script and run it using SQLCMD or run the scripts individually from Management Studio. Running the previously mentioned scripts separately using SQLCMD is not running them in the same session. Running the scripts via Management Studio constitutes running them in the same session. |
22sl120i.sql |
Sets the flag for the installed modules and options using 7idef.sql |
26sl120i.sql |
Populates the system basic data using 7idef.sql |
40sd120i.sql |
Contains a statement to populate several tables with seed data using 7idef.sql |
50sc120i.sql |
Creates table constraints, indexes, and sequences |
60spr120.sql |
Creates database procedures, functions, and views |
70stg120.sql |
Creates database triggers |
80ed120i.sql |
Seed data manipulation |
dbinstall.sql |
Sets up privileges to run HxGN EAM functions |
-
To uninstall the Microsoft SQL Server database, back up the entire database, and then drop it. We strongly recommend that you back up the database before you drop it. See the Microsoft SQL Server documentation for more information on how to back up the database.
-
As a part of regular database maintenance, you must periodically remove redundant rows from sequence tables. To clean the database, open the Management Studio and execute:
execute p_cleanout_id_tables