Migrating Enterprise Version 2.9 Databases to Version 3

Migrating Enterprise Version 2.9 Databases to Version 3

This article documents how to migrate your existing Version 2 DataSight database to the new Version 3 database structure.  It assumes that you are using DataSight Version 2.9.6, so please contact us if you are using an earlier version of DataSight Enterprise or DataSight Desktop.  You will need to have access to have Administrative access to your MS SQL server instance.

The steps in migration will be as follows:

  • Backup your existing Version 2 database(s) prior to migration.
  • Install DataSight Administrator in the MS SQL Server. 
  • Run DataSight Administrator.  You will need to login as an MS SQL Server sysadmin to have the correct privileges for creating databases in your MS SQL server.
  • Create a new DataSight Version 3 database by selecting the  “Create Database” option from the New Database menu. This will create an empty DataSight Version 3 database that will be ready for migration from the version 2 db. If you have multiple Version 2 databases, you should ideally create one Version 3 database for each.
  • Use Administrator to set the different users that will be accessing the DataSight databases through “User Management”.
  • Download a Migration tool.
  • Once you download and install Migrator on the server, you will see the login screen with Source and Target, where you will identify which Version 2 database you are migrating from and which Version 3 database you are migrating into. Use a sysadmin to login (sql authentication) and run the migration by selecting ALL (Level -> Audit Log). 

    The Administrator must know the Server Names, Databases and log on details to continue.

    It is critical that the databases reside either on linked servers or on the same MS SQL server.

  • Once the Administrator has successfully logged in, they can select which areas of the database they wish to migrate. In most cases the migration will be for all Tables of the DataSight Enterprise 2.9 database. The Administrator can select all by ticking the box on the left in the header row.

  • After selecting all the Administrator can then select Start and each Table selected will be migrated in turn. Each Table will have a start time and end time of the migration as well as the Status.

  • The Administrator who logged into DataSight Administrator to create the blank database will have their log on details stored as the Administrator of the database and has access to the migrated DataSight Version 3 database.

  • When the migration is running, you will see each migration item outputting a message on the Log screen. If there is an error (for example you are trying to migrate between different servers) it will come up on the screen. Data migration can take a long time.  If you are migrating between servers, you will need to create a linkedserver between the target and source which affords SQL authentication access.
  • Once migration is complete, you can view the data from any DataSight version 3 “Client” installation. 
  • Please note that graphs in saved views and import templates cannot be migrated from Version 2.
  • Users are not migrated and application security needs to be re-established with consideration given to the new permissions available in DataSight Version 3.