Have a Question?
Categories
< All Topics
Print

Migrating the Collective Data Server and Database – MS SQL

Note: If this installation is on a Windows 8, 7, Vista PC or Windows 2008 Server please shut off UAC prior to the migration. This can be done by going to Start >> Run . Type msconfig and click on the tools tab. Then, click the launch button to open the UAC window and shut it off. Next reboot the system. Windows secondary log on service must be enabled also. Go into control panel-admin tools-services and enable the secondary log on service.

1) Backup your current fleet database, use the SQL Server management studio or what ever internal process you use. Copy this on to a disk.

2) Copy the collective data folder off of the current system running the collective server.

3) Restore it on to the file server

4) Go to C:\Program Files\Collective Data\collectiveServer 5.5 and launch install.bat

5) Go into services and verify the collective server service is installed and running.

6) Go to the new SQL server, create a fleet database and restore the backup you made from the original server.

7) Create a system DSN ODBC connection to the database using a SQL account. If you are using 64 bit MS SQL please reference the following article http://support.microsoft.com/kb/942976

8) Create a system DSN ODBC connection to the database using a SQL account for each station running a collective data client.

9) From the system running the collective server launch http://localhost:8080/admin, chose the datasource administrator and verify the settings are correct.

10) Make sure to point all existing clients to the new server when logging in by launching the client and clicking on the adv. button and changing the server host. Next point the system to the new database by going to system-database administrator and changing the ODBC connection name if different, and the username and password if a different one was created on the new SQL Server.

On the server launch the system admin page, http://localhost:8080/admin and click on the database admin and point the admin page to the new database location.

Table of Contents