Database Upgrades

  1. If you are installing a new version of the software, or a database upgrade is required and you are logged in as an admin user, the following screen may appear:

  2. Before you carry out an upgrade, implement a change freeze for your users; ensure that you have taken backups of all databases and have a roll-back plan in place. For more details see Upgrade Roll-back Plan.
  3. A database upgrade allows you to upgrade the Micromine Geobank Core Component.

    4. Note that a warning message will be displayed if your database is not compatible with SQL server 2016sp2 or higher. This is the minimum requirement for Micromine Geobank as specified in the System Requirements.

    All existing objects and their usage data will be migrated to a new independent set of configuration tables (legacy sets can be purged later).

    Upgrades to the Core component will add new configuration tables for each major or minor version, creating independent sets of configuration objects.

  4. The Micromine Geobank Sample Tracker Component may also be upgraded. If this option is selected, (ST) system tables may also be added to your content database, or be noted as missing (these should be added manually). Click here for details about the required Sample Tracker Data Model.

    5. When you have made your selections, click Next to continue.

    Note: The current technology used by Micromine Geobank for accessing the Sample Tracker tables uses an all or nothing approach. This may mean that some tables or columns which are unnecessary in your case need to be added to the database to support Sample Tracker. This technology is being reviewed to provide more flexibility in future.

  5. The Configuration database may have one or more Model databases within it:

    6. In the above example, there is one Configuration (SYSTEM) database, and one MODEL database within it.

    Micromine Geobank will scan all data sources prior to the upgrades.

    If a data source is unavailable, it will be shown as Unknown:

    In the event of connection problems, the Connection timeout (seconds) value (on the Environment Settings page of the Configuration Database Connection Property Editor) may need to be increased. Connection parameters and their values are specific to particular providers, servers and drivers.

    If you are running (potentially slow) queries on large datasets you may need to increase the Command timeout (seconds) value.

    If you are performing transactions on very large datasets you may also need to increase the Transaction timeout (minutes) value, or even set the value to zero to disable any timeout (a warning is displayed since a zero time-out value may mean transactions take an indefinite time to complete).

    Property Editor: Environment Settings

  6. To perform a SYSTEM upgrade only (i.e. you do not use Sample Tracker or you prefer to use your own databases), select a configuration database but do not select the MODEL databases within it.

    7. Note: Both the Configuration patch and the Sample Tracker patch will apply any structural changes and data additions to the Configuration database. The set of Configuration tables used by Micromine Geobank 2018 (or earlier) and their data are unaffected, hence the earlier version will continue to work; however, any configuration changes made in the earlier version will not be transferred to the Micromine Geobank 2024 configuration once the upgrade has been completed (See: Version & Upgrade Management).

  7. To perform a MODEL upgrade, select the databases you want to upgrade. The Configuration database they belong to is automatically selected, since an upgrade of these databases requires an upgrade of the SYSTEM database.

    8. Note: There are no structural changes to the Sample Tracker Model between Micromine Geobank 2020 and Geoank 2024. For further information on the upgrade, see: Sample Tracker Data Model

  8. When you have selected the databases you want to upgrade, click Start. The time it takes to upgrade will depend on the number of databases you have selected and their size.

    9. Table mappings applicable to each installed module will also be validated as part of the upgrade process.

    You may need to update the system table and column mappings if:

      • a mapping exists but the mapped column name does not exist in the database.

      • a column needs to be mapped to a column in the database.

    Download, unzip, and import the following dataview to assist in verifying and adjusting your system mapping for Micromine Geobank v10+ (GB 2017 - GB 2020). The dataview has an instruction page: System Mappings Dataview

  9. When the upgrade is complete, you will be given the option to either copy the log to the clipboard or save the log to a file.

    10. While these are optional, it is recommended that you save a log file if errors or warnings are reported during the upgrade process.

  10. If the database upgrade fails, then:
    • Review the log for instructions on any mapping issues or required fields which need to be added. Details on the requirements are in Step 3 and a mapping management tool can be downloaded - see the note under Step 8
    • A UNIQUE KEY constraint 'UC_GB110_CONFIG_OBJ' was introduced in Micromine Geobank 2020. If you receive the following error lwhen upgrading the SYSTEM database:

      • Violation of UNIQUE KEY constraint 'UC_GB110_CONFIG_OBJ'.
      Cannot insert duplicate key in object 'GB.GB110_CONFIG_OBJ'.
      The duplicate key value is (TGbConfigDataView, Edit Sample Despatch).
      The statement has been terminated.

      You will need to delete or rename the duplicated object in order for the upgrade to complete successfully.

    • If the upgrade failed due to a timeout when upgrading a large database, open the data source properties for the database and set the Transaction Timeout (under Environment settings) to 0. When you click OK you will be prompted to restart the upgrade. (0 means no timeout).
    • An upgrade can be manually reinitialized and re-started by executing Micromine Geobank with -F as a command line parameter to 'force' a version upgrade
    • The Micromine Geobank support team have additional tools and scripts and can assist you with questions about required fields or mappings. Please email support@micromine.com for assistance.