Generate the Full MineMarket SQL Script

Use this activity to generate the required full SQL script to build the MineMarket database tables.

Note: This activity is optional. Full scripts for Microsoft SQL Server and Oracle are provided with the setup package.

Activity Steps

  1. Launch the DBScriptGen.exe application, located in the same folder as the MineMarket application.

    The Database Script Generator opens.

  2. Specify an output file name:
    1. Click the ellipsis (...) next to Output File.
    2. Enter the name of the SQL script to be generated (for example, MineMarket_V5.6.x.SQL).
    3. Click Save.
  3. Specify the MineMarket DLL:
    1. To remove any pre-existing DLL files in the assemblies list, select the DLL and click Remove.
    2. Click Add.
    3. Select the BulkTrak.Component.DLL file in the MineMarket installation folder.
    4. Click Open.
  4. Select the Database Type.
  5. To drop existing tables in the database, check Include Drop Statements.

    Important: For a new installation of MineMarket, data does not usually exist in the target database, in which case, including or excluding drop statements makes no difference.

    However, if data already exists in the target database, it is strongly recommended that you back up the database prior to running the generated SQL script.

  6. Check Use Double Byte Characters.

    Note: Double-byte characters are required for non-alphanumerical character-based languages (for example, Chinese, Japanese, Korean). Oracle databases support double-byte characters by default. Since MineMarket 5.2.0, all SQL databases are converted to support double-byte characters. Fields with the varchar character data type will use nvarchar, and fields with the text character data type will use nvarchar(max).

  7. Uncheck Include Report Manager Tables.
  8. Uncheck Generate Data Dictionary Tables.
  9. Click Generate.

    The Generation complete dialog box displays when finished.

    Note: Any warnings of the type "Foreign key field name mismatch" indicate that the names of the key columns for the parent and child tables are different. These do not impact script functionality, and can be ignored.

  10. Click Close.