How to transfer or migrate data from a corrupt eXpress database to a clean database


Article ID: 179967


Updated On:


Deployment Solution Ghost Solution Suite





How do I create a new eXpress database from a corrupt eXpress database, still keeping all of my data such as jobs, computers, settings, and history?

There are a lot of situations where creating a brand new database might resolve an issue with Ghost Solution Suite 3 (hereafter GSS); most of the time the data from the previous database will still be wanted because is contains jobs, computers, settings, and history. Sometimes this data is what is causing the problem with the database, but sometimes it is not. When the database is having problems because of stored procedures, permissions set incorrectly, or other corruption other than data, the following steps can be very useful.

NOTE: This article pertains to Deployment Solution 6.9 as well, and the steps are identical except for the installer download location.


  1. Stop all Altiris services
  2. Rename your current eXpress database to eXpress2
  3. Create a GSS installation directory. Normally when running the installation file for GSS, it will extract these files to a folder on the root of your drive called "DSSetup". Do a search on your server to determine where this is at. If you do not have a DSSetup folder (or its equivalent) you will need to download the GSS installation file from the Free Trial section on site (select Deployment Solution for Clients). Once downloaded run the installer and select Extract Only.
  4. Run the executable "Server.exe" from the DSSetup folder:  While going through the wizard follow these steps:
    1. Click Next at the welcome screen
    2. When it asks you to "Select the Components to be Installed" put a check mark next to eXpress Database only (uncheck the other two if they are selected).
    3. The next step it will ask for a username. Most likely you will be using Windows Authentication, in which case leave the username "~NTAuthentication~". If you know that you are using a SQL server account instead, use that username.
    4. When the wizard asks for a password, if you used "~NTAuthentication~" as the username, leave the password as it is. If you entered in a SQL username, enter the password here. WARNING: this field is not secure, the password will be displayed as you type it!
    5. The step SQL Server Database Name will already have the name "eXpress" entered. If you have deleted the previous database completely, you can keep that name, but normally you will want to enter a new name (such as eXpress2 or eXpressNew). Renaming your old eXpress database will not allow you to then name the one one eXpress as SQL leaves the old file names.
    6. At this point the dbinstaller will run and will create the new database; if the installation works properly, the last step will be a confirmation where you need to click on Finish.
  5. Verify that the new database works correctly (even though it might not have all of the jobs, settings,  and computers that it had before).
    1. Check ODBC settings—the GSS should be using the new database, even if the old database is still still there.

      Note: You can switch back and forth between the old and new database easily by simply changing the ODBC settings for the "Altiris eXpress Database" System DSN. This can be done in the Server's Windows operating system under Start > Control Panel > Administrative Tools > Data Sources (ODBC) > System DSN tab. If you select the Altiris eXpress Database DSN and click on Configure, you can go through a wizard to change its settings. On the third step of the wizard there is an entry that says Change the default database to. This is where you can change GSS to point to another database.
    2. Launch the GSS Console and send sample jobs to a few workstations. If the problem you are troubleshooting is still occurring, it might not have anything to do with the database and you should probably go back to your original database. Step 6 will not help.
  6. Download MigrateData.sql file in the attached files, and execute the query using SQL Query Analyzer.
  7. Verify that Deployment Server works correctly.

Now that the data has been successfully transferred over, restart all of your Deployment Server services and check to see if there are still errors or problems with the new database. Open the console and send sample jobs to your workstations.

If there now are problems with the new eXpress database after importing over the old data, the problem might be caused by the data in the tables. If this is the case, you might need to repeat step 2 to re-create the database, but you will not be able to import over the new data. You can try using the built-in export tool to export computers and jobs, then import them into the new database, in some cases this has cleared up corruption, but if this doesn't work then the only option left is to revert to a backup if you have one (hoping the backup doesn't have corruption as well), or to re-create all of your jobs and computer group structure.


MigrateData.sql get_app
MigrateData.sql get_app