How to Migrate Jet Analytics to a New Server?

Planning to migrate Jet Analytics to a new server? Whether you’re upgrading hardware, moving to a new environment, or restructuring your setup, it’s essential to handle the migration carefully to avoid data loss or downtime. In this guide, we’ll walk you through the entire process—from transferring your project repository to configuring services—so you can ensure a smooth, hassle-free migration.

Step 1: Move the Project Repository

Your Project Repository holds all the instructions needed to rebuild Jet Analytics. It’s stored in a SQL database and is the only database you need to move.

How to do it:

• Take a SQL backup of your current project repository.

• Restore it to your new server using SQL Server Management Studio (SSMS).

Step 2: Install Jet Data Manager (JDM)

Now that the project repository is on the new server:

• Download and install the latest version of Jet Data Manager from the insightsoftware website.

• During setup, you’ll be asked for the location of your project repository.
  ➤ Choose the one you just restored.

• If prompted to upgrade the repository, click Upgrade and select Web Service as the method.

Step 3: Update Project Configuration

Make sure everything is pointing to the right locations on the new server:

1. In JDM, right-click your project name and choose Connection Manager.

2. Click the pencil/edit icon next to:

   • Staging Database

   • Data Warehouse

   • OLAP Server

3. Update the server names (use localhost if the databases are on the same machine).

4. Click Create to set up fresh staging and data warehouse databases.

5. (Optional) If you don’t want SQL to store files on the C:\ drive, you can:

   • Detach the databases

   • Move the files to your preferred drive

   • Reattach them using SSMS

6. Click Test Connections to confirm all are green (working).

Step 4: Set Up Jet Data Manager Scheduler Service

This service runs the scheduled updates for your cubes and warehouse.

To configure it:

1. Open the Windows Services app.

2. Find Jet Data Manager Scheduler and open its Properties.

3. Set Startup Type to Automatic (Delayed Start).

4. Under Log On, use a service account with the right permissions:

   • Must have db_owner rights on:

     • Project Repository

     • Staging Database

     • Data Warehouse

   • Must be an administrator in SQL Server Analysis Services (SSAS)

5. Click Start to launch the service.

Having trouble?
If the service starts and stops immediately, log into the server as the service account, open JDM, and point to the project repository. This creates the necessary config files. Then you can log back in with your own user account and start the service successfully.

Step 5: Deploy and Execute the Project

Now it’s time to bring everything to life:

• Open JDM and click Manual Deployment and Execution.

• Hit Start to begin.

This will create your SSIS packages and populate your data warehouse and cubes.

Your Jet Analytics environment is now successfully migrated to the new server. If you are migrating jet analytics to cloud: Follow our Guide for moving Jet Analytics to cloud. 

If You Need Any Help, Contact us Now!