Introduction

Tutorials

Reference

Upgrading GeoData Manager to a newer version

This describes how to upgrade GeoData Manager to a newer version. To install GeoData Manager for the first time, or to uninstall GeoData Manager, see here.

It is important that the IT department use this section of the help guide develop a protocol for upgrading GeoData Manager, and the subsequent upgrades of databases.

Upgrading GeoData Manager to a newer version

We regularly upgrade GeoData Manager to provide new features and fix bugs, and email you about each release. We recommend that you upgrade your GeoData Manager each time a new version is released.

Note that during an upgrade, GeoData Manager's preferences, your key registration and the dongle operation are not affected.

Part 1 - Prepare for the upgrade:

  1. Find if you need to upgrade your databases: As you install your GeoData Manager upgrade, you might need to upgrade your databases to a new version as well. Our email will tell you if you need to do this, or you can find out here.

  2. Backup your databases.

  3. Upgrading will always create a new sample database, called atlantis.mdb. Any existing sample database will be removed from the database manager window and will be renamed from atlantis.mdb to atlantis_Vnn_yyymmdd.mdb. Both databases are stored in your application data, not your program files. If you want to continue to use that existing sample database, add it to the database manager window after you have finished the upgrade.

  4. You will use the Access test database that you created earlier during installation see here. If you have a network, ensure this is on the server.

  5. If you need to upgrade your databases and you have any SQL server databases, create an SQL server test database: Back up your biggest or your most frequently used SQL server database and store it on the server if you have a network.

  6. Decide which computer to install GeoData Manager on first and decide which computer you will run GeoData Manager on first:

    Configuration 1 (one computer): This computer.

    Configuration 2 (network, GeoData Manager on user computers): Install first and run first on a convenient user computer.

    Configuration 3 (network, GeoData Manager on server): Install first on server, run first on a convenient user computer using Remote Desktop Connection.

    Configuration 4 (network, GeoData Manager on server and on user computers): Install first and run first on a convenient user computer.

    ... and a convenient user computer is one where you can log in and see all the main databases in the Database Manager window (so you can upgrade them easily). If you have any SQL server databases, you must be a dbo user, or alternatively you and other GeoData Manager users are all members of a db_owner role for these databases.

Note: If you have a network, the above three steps ensure that when you test GeoData Manager it will be on a different computer to the test database(s), so that when you test GeoData Manager you will test the network connection too.

Part 2 - Install GeoData Manager and test an Access database:

  1. Go to the GSDS website GeoData Manager download page. Download the latest version of GeoData Manager (gsds_gdman_n_n_n_n.msi),

    If you have GeoData Manager installed on more than one computer, put gsds_gdman_n_n_n_n.msi on a USB stick to simplify installation.

  2. Install GeoData Manager once, on the computer you decided to install GeoData Manager on first: run gsds_gdman_n_n_n_n.msi. You don't need to uninstall the previous version.

  3. Start GeoData Manager on the computer you decided to run GeoData Manager on first.

  4. GeoData Manager shows the Database Manager window. If necessary, use Add DB to connect to the Access test database (see above). For the description (name), enter Access test DB.

  5. In the Database Manager window, double-click Access test DB to open it.

  6. If you need to upgrade your databases, GeoData Manager asks if you want to upgrade: click OK. If upgrading gives an error, stop now and contact GSDS.

  7. Briefly test that GeoData Manager works properly:

    Run a few basic tests, for example navigate from node to node, display a graph, edit a data set, display a multiple graph.

    To see new features in the new version of GeoData Manager, click Help, click About GeoData Manager and click the tab Change Log. Briefly check some of the new features.

    Note: If IT personnel are not familiar with GeoData Manager then a competent GeoData Manager user should run these tests. These tests are to confirm there are no fundamental problems, such as with the operating system or database setup. More extensive testing is not required – if errors exist, they are likely to be in fairly obscure parts of the program, and may not be found in any reasonable testing.

Part 3 - If you need to upgrade your databases and have any SQL server databases, test one:

  1. Warning: You must have Admin permission plus either be a dbo user or you and other GeoData Manager users must all be members of a db_owner role for this database read more.

  2. Open the Database Manager window and use Add DB to connect to the SQL server test database that you created above. For the description (name), enter SQL server test DB.

  3. In the Database Manager window, double-click SQL server test DB to open it.

  4. GeoData Manager asks if you want to upgrade; click OK. If upgrading gives an error, stop now and contact GSDS.

  5. Again, briefly test that GeoData Manager works properly.

Part 4 - If you need to upgrade your databases, upgrade your main databases now now:

Part 5 - If you have GeoData Manager installed on more than one computer, install GeoData Manager on the other computers:

  1. On each other computer, run gsds_gdman_n_n_n_n.msi. You don't need to uninstall the previous GeoData Manager.

  2. If you need to upgrade your databases, and if users have private test or demo databases on their user computer, open each in GeoData Manager and GeoData Manager will upgrade them. Note that for SQL databases, you need to be logged in as an Administrator.

Part 6 - Finally:

  1. Keep the Access test database for the next upgrade.

  2. If you have any SQL server databases:

    In the Database Manager window, use Remove DB to remove SQL server test DB from the list.

    Use Microsoft SQL server to delete the SQL server test database.

Note: During an upgrade, GeoData Manager might automatically upgrade its preferences files read more.

The database upgrade log

Each time you upgrade a database, GeoData Manager writes an entry in a log of database upgrades in that database. To see the log, go to the node Logs: Database Upgrades in the database tree.

The fields are:

Field Data
VersionNumber Of the upgraded database
LastModified The data of the upgrade
UserName The user who did the upgrade
UpgradedTables The database tables that were changed by the upgrade; read more about database tables

Finding what's new in GeoData Manager

If you skip upgrades

If you skip installing a few new versions of GeoData Manager and then install the latest version:

Note: You can download and install earlier versions of GeoData Manager from the GSDS web site, but you should never run a version of GeoData Manager whose database version is earlier (lower) than your database version.

Between upgrades, the versions of all your databases are normally the same, and correct for the version of GeoData Manager that you are running. However, a database version could be earlier (lower) than the rest:

In this case, open that lower-version database in GeoData Manager and it should automatically upgrade the database to the correct, new version, as discussed above.


Understanding version numbers

The program and database version numbers are different. This section tells you how to find these version numbers.

Finding the version number of your current GeoData Manager program

Each release of GeoData Manager has a version number, of the form n.y.mm.dd, where:

Letter Means
n A major release number, eg 5
y Related to the year it was released; 9 means 2014
mm The number of the month it was released; 8 means August
dd The day of the month it was released; 21 means the 21st

To find the version of GeoData Manager that you have:

Finding the version number of a database

Each of your GeoData Manager databases has a version, a number, for example 31, that reflects the structure of the database:

To find the version of one of your databases: In GeoData Manager, click File, click Database Manager to open the Database Manager window, then click Version.

![](Images/db_Home.png)

You see the versions down the right.

Finding the newest GeoData Manager and database versions

To find the newest available version of GeoData Manager and the version of its database:

  1. Click Help, then click Check latest version ....

  2. GeoData Manager connects to the internet and displays a page:

    • Latest version is the latest version of GeoData Manager available, for example Version 5.4.8.21

    • Database (DB) version is the database version used by the latest version of GeoData Manager, for example 31.

If Database version is higher than version of your databases then if you upgrade to this version of GeoData Manager then GeoData Manager will automatically upgrade your databases.