UPGRADING SEER-HD 2.0.5.0 TO SEER- HD 3.1.5...For users who work with multiple copies of access database. We recommend configuring the DSN to point to the SEER-RDB.mdb file. This approach

222 N. Sepulveda Blvd., Ste. 1700 El Segundo, CA 90245 o. +1 310.414.3222 f. +1 310.414.3220 www.galorath.com

UPGRADING SEER-HD 2.0.5.0 TO SEER-

HD 3.1.5.0

TABLE OF CONTENTS

Upgrading a Local Instance of SEER-HD.......................................................................................................... 2

Notes about SEER-HD 3.1.5.0 ...................................................................................................... 2

Scenario 1: SEER-HD 2.0.5.0 only contains default data ............................................................. 2

Scenario 2: SEER-HD 2.0.5.0 contains ISBSG or custom data ...................................................... 3

Create a new SEER-HD ............................................................................................................. 3

Backup the old database ......................................................................................................... 3

Upgrade the old Access database ........................................................................................... 4

Configure the 32-Bit SEER-HD DSN .......................................................................................... 6

Upgrading a Server Instance of SEER-HD ....................................................................................................... 8

Required Administrative Privileges ............................................................................................. 8

For SQL Server and SQL Express .............................................................................................. 8

Configure SEER-HD to use Windows Authentication .................................................................. 9

Upgrade the old SQL Database .................................................................................................. 11

http://www.galorath.com/


UPGRADING A LOCAL INSTANCE OF SEER-HD

NOTES ABOUT SEER-HD 3.1.5.0

SEER-RDB.mdb file has been renamed to SEER-HD.mdb

The MDB file will no longer be installed at the “ProgramData” location. Instead, it will be installed

at the “Public Documents” location.

Old location: C:\ProgramData\SEER\SEER-RDB\SEER-RDB.mdb

New location: C:\Users\Public\Documents\SEER\SEER-HD\SEER-HD.mdb

SCENARIO 1: SEER-HD 2.0.5.0 ONLY CONTAINS DEFAULT DATA

1. Inside the SEER-HD folder, run setup.exe

2. HD 3.1.5.0 installer will overwrite the existing SEER-HD DSN and point to the new SEER-HD.mdb

file locating at the above directory



Since SEER-HD 2.0.5.0 only contained default data, the installation is now complete. SEER-HD 3.1.5.0

contains the same default data as SEER-HD 2.0.5.0.

SCENARIO 2: SEER-HD 2.0.5.0 CONTAINS ISBSG OR CUSTOM DATA

The MDB file names are in their default names. If you are an experienced SEER-HD user who has multiple

MDB files, feel free to upgrade whichever file you need to. The steps are still the same.

CREATE A NEW SEER-HD

1. Inside the SEER-HD folder, run setup.exe

2. HD 3.1.5.0 installer will overwrite the existing SEER-HD DSN and point to the new SEER-HD.mdb

file locating at the above directory

Since SEER-HD 2.0.5.0 contains custom data, we will have to take an extra step and upgrade the old MDB

file (SEER-RDB.mdb) manually.

BACKUP THE OLD DATABASE

We recommend creating a backup of the original SEER-RDB.mdb file before upgrading it to

the latest version.

1. Make a copy of the SEER-RDB file located here and rename the copied file.

C:\ProgramData\SEER\SEER-RDB\SEER-RDB.mdb



UPGRADE THE OLD ACCESS DATABASE

1. Inside the SEER-HD folder, run RDBupgrader.exe

2. Select the option to “Upgrade older version of HD to version 3.1.5.0” and press “OK”



3. Press “File…” and locate the MDB file in the below directory

C:\ProgramData\SEER\SEER-RDB\SEER-RDB.mdb

4. Click on “Upgrade” and click “Yes” on the next message

5. Once complete, you will be prompt with the following message.



6. Starting with SEER-HD 3.1.5.0, SEER-HD will be installed at the “Public Documents” location.

Move the SEER-RDB.mdb file from the “ProgramData” location to the “Public Documents”

location alongside with the new SEER-HD.mdb file.

Old location: C:\ProgramData\SEER\SEER-RDB\

New location: C:\Users\Public\Documents\SEER\SEER-HD\

For users who work with a single copy of the access database, we recommend deleting the “SEER-

HD.mdb” file. Then rename “SEER-RDB.mdb” file into the ‘new’ “SEER-HD.mdb”. After renaming, the

setup is now complete.

For users who work with multiple copies of access database. We recommend configuring the DSN to

point to the SEER-RDB.mdb file. This approach will need admin privledges and the steps are provided in

the below section.

CONFIGURE THE 32-BIT SEER-HD DSN

After installing SEER-HD3.1.5.0, the default SEER-HD DSN will be pointing to the newly created SEER-

HD.mdb. Follow the steps below to ensure the DSN is pointed to the upgraded MDB file we performed

above.

1. Navigate to the following location and launch odbcad32.exe.

C:\Windows\SysWOW64\odbcad32.exe

2. Click on the “System DSN” tab and find the DSN that is associated with the SEER-HD instance. By

default, it is called “SEER-HD”

3. Select the DSN and click on “Configure” on the right.



4. Click “Select…” and select “SEER-RDB.mdb” as the file

5. Press “OK” at this screen and again at the next screen

6. The setup is now complete. The 32-bit DSN is now pointing to the previous SEER-RDB database,

which is now upgraded to version 3.1.5.0.



UPGRADING A SERVER INSTANCE OF SEER-HD

REQUIRED ADMINISTRATIVE PRIVILEGES

To upgrade an SQL Server instance of a SEER-HD database, the user must have DBMS

administrative privileges for the target instance of the SQL Server DBMS where the database is.

The SEERHD SQL Server Database Set-Up Utility assumes the user has the appropriate SQL Server

administrative privileges.

FOR SQL SERVER AND SQL EXPRESS

For SQL Server and SQL Express, a user will have the required administrative privileges to

upgrade a database.

The user account must belong in either of the following roles:

The windows user is part of the server role “sysadmin”



The window user is part of the database role “db_owner”

SEER-HD SQL cannot be upgraded using a SQL Server login. Even if the SQL login belongs in

the roles mentioned above. SQL Server login can be only used to create a brand new SEER-

HD SQL instance.

CONFIGURE SEER-HD TO USE WINDOWS AUTHENTICATION

SEER-HD SQL can only be upgraded via windows authentication. Please follow the steps below to ensure

the SEER-HD SQL DSN is set correctly. System DSN can only be configured with a windows account with

admin privileges

1. SEER-HD DSN is created as a 32-bit DSN. Navigate to the following location and launch

odbcad32.exe.

C:\Windows\SysWOW64\odbcad32.exe

2. Click on the “System DSN” tab and find the DSN that is associated with the SEER-HD instance. By

default, it is called “SEER-HD”

3. Select the DSN and click on “Configure” on the right.

4. Click “Next” to go to the next page

5. At this screen, make sure you are set to the first option to use “Windows Authentication”



6. Click “Next” then make sure the default database is set to “SEER-HD”



7. Click “Next” and then hit “Finish.

At any point if the DSN configuration fails to continue, please check with the database admin

to ensure your windows account is assigned to the right database.

UPGRADE THE OLD SQL DATABASE

1. Inside the SEER-HD folder, open the SEER-HD SQL folder and launch setup.exe

2. Choose the second option for upgrading an existing SEER-HD



3. The default DSN name will be “SEER-HD”, feel free to change it if needed.

4. Click “Next” and confirm the setup. Once the upgrade is finished, you will be prompt with the

following message.



8. The installation is now complete. Any custom data in the original database will be in the

updated database.

If you have any installation issues, please contact the Galorath support team at 310-414-3222 or email

[email protected]


mailto:[email protected]