Installing a new SQL server database - HxGN EAM - 12.0.1 - Installation & Upgrade

HxGN EAM Application Installation
Language
English
Product
HxGN EAM
Search by Category
Installation & Upgrade
HxGN EAM Version
12.0.1

Only Microsoft SQL Server database administrators or equivalent should perform any function described in this section.

Ensure that the Microsoft sqlcmd utility is executable from a command prompt on this computer. After connecting to the database, issue any TRANSACT-SQL command to ensure that it is working properly.

See the following syntax when executing the Microsoft sqlcmd utility. See the Microsoft SQL Server documentation for more information.

usage: sqlcmd

[-U login id]

[-P password]

[-S server]

[-H hostname]

[-E trusted connection]

[-d use database name]

[-l login timeout]

[-t query timeout]

[-h headers]

[-s colseparator]

[-w columnwidth]

[-a packetsize]

[-e echo input]

[-I Enable Quoted Identifiers]

[-L list servers]

[-c cmdend]

[-D ODBC DSN name]

[-q "cmdline query"]

[-Q "cmdline query" and exit]

[-n remove numbering]

[-m errorlevel]

[-i inputfile]

[-r msgs to stderr]

[-V severitylevel]

[-p print statistics]

[-o outputfile]

[-O use Old ISQL behavior disables the following]

[-b On error batch abort]

<EOF> batch processing

Auto console width scaling

Wide messages

default errorlevel is -1 vs 1

[-? show syntax summary]

If you are installing on a machine that has Windows Server 2019, you must add setupwin32.exe as an exception to the Data Execution Prevention List. This exception can be removed once installation is complete.

  1. Insert the HxGN EAM SQL Server Database Installation CD into the proper drive.

  2. Locate and right-click the Setupwin32.exe file and run as administrator.

    If you are installing from a drive other than D:, substitute that drive for D: in these instructions.

  3. Select a language to use, and then click OK.

    By selecting a language, you are selecting a language to be used during the installation, not a language to be used by the SQL Server database.

  4. Click Next.

  5. Enter the CD Key for the product, and then click Next.

  6. Select I accept the terms of the license agreement if you agree to the terms, and then click Next.

  7. Select install a new database.

  8. Click Next.

  9. Ensure that your computer meets all installation requirements, and then click Next.

  10. Specify the directory for database installation processing (the logs and all scripts are created in this directory), and then click Next.

    All database configuration scripts and installation logs are created and processed in the chosen directory.

  11. Specify this information:

    Host Name - Specify the Microsoft SQL Server name.

    If your server does not have specific instances installed, you do not have to enter a value for Instance.

    Instance Name - Specify the name of the database instance, if any.

    Listener Port - Specify the Microsoft SQL Server listener port.

    System Administrator User - Specify the system administrator username of the account that you will use to create the database.

    System Administrator Password - Specify the system administrator password of the account that you will use to create the database.

    We strongly recommend that only SQL Server database administrators or equivalent with accesses to create and configure databases, create users, and grant privileges install and configure the SQL Server database.

  12. Click Next.

  13. Specify this information:

    Login - Specify the database login that you will use to connect to the EAM application.

    Password - Specify the database password that you will use to connect to the EAM application.

    Database Name - Specify the name of the database that will be used for the EAM application.

    You cannot enter an existing database name for Database.

  14. Click Next.

    Specify information for both the Primary Data File (the starting point of the database) and the Log File (the file used to recover the database).

  15. Specify this information:

    Name - Specify a unique name to identify the database file.

    Path - Specify the valid path on the database server.

    Size (MB) - Specify the size of the database file.

    Max Size (MB) - Specify the maximum size of the database file.

    If you need unrestricted file growth, enter UNLIMITED for Max Size (MB).

    Name - Specify a unique name to identify the log file.

    Path - Specify the valid path to the log file on the database server.

    Size (MB) - Specify the size of the log file.

    Max Size (MB) - Specify the maximum size of the log file.

    If you need unrestricted file growth, enter UNLIMITED for Max Size (MB).

  16. Click Next.

  17. Specify this information:

    Name - Specify a unique name to identify the index file group.

    Path - Specify the valid path to the index file group on the database server.

    Size (MB) - Specify the size of the index file group.

    Max Size (MB) - Specify the maximum size of the index file group.

    If you need unrestricted file growth, enter UNLIMITED for Max Size (MB).

  18. Click Next.

  19. Specify the path to the Binn directory for your Microsoft SQL Server instance.

    In future installers this screen will be removed.

  20. Click Next.

  21. Specify a CD key for the Mobile user license (optional) if you have purchased a license for Mobile from HxGN, enter the CD key for the product.

  22. Specify a CD key for the Connector user license (optional) if you have purchased a license for Connector from HxGN, enter the CD key for the product.

  23. Specify a CD key for the Barcoding user license (optional) if you have purchased a license for HxGN EAM Barcoding from HxGN, enter the CD key for the product.

  24. Specify a CD key for the Requestor user license (optional) if you have purchased a license for Requestor from HxGN, enter the CD key for the product.

  25. Click Next.

  26. Select the language(s) to implement, and then click Next.

  27. Select Position for a position to allow multiple assets as children. Select Tags for a position to allow only a single asset as a child.

    Positions and assets are types of equipment that are used within HxGN EAM. Pieces of equipment are entities for which you store data and create work orders. Equipment can be of many different types, but the four main types are locations, systems, positions, and assets.

    Locations, systems, positions, and assets form a hierarchy of equipment information, with locations at the top of the hierarchy and assets at the bottom. Data is shared among the levels of the equipment hierarchy. For example, data for a work order performed on an asset is also stored in the position, system, and location equipment to which the asset belongs. This data sharing allows you to track assets and their performance in detail and under differing conditions, to evaluate the performance of entire systems, and to assess the effect that locations and positions have on systems and assets. See the HxGN EAM User Guide.

    Thus, by selecting Position, a position in the system can have multiple assets as children below it in the hierarchy, but by selecting Tag, a position in the system can only be linked to one asset.

  28. Specify this information:

    Price Level - Choose one of the following options:

    • P - Select to record prices at the part level.

    • S - Select to record prices at the stock level.

      Default Language - Select the default language for the EAM application.

      Default Currency - Specify the currency.

  29. Click Next.

  30. Click Next. A message is displayed asking whether you choose to run the database scripts manually or to have the database scripts created and automatically run.

  31. Click Yes to create and automatically run the database scripts, or click No to run the installation database scripts manually. If you click Yes, the database scripts are created and run and the final installation dialog box is displayed. If you click No, the database scripts are created, but you must run the scripts manually.

  32. Click Finish.

    If you selected to automatically run the database scripts, examine the log files in the log directory you created earlier in this section for errors.