Perform the steps below to perform an ANSI_NULLS table migration:
Stop all web services that communicate with the database.
If your organization uses web services made by other parties, stop these as well.
Stop all windows services that communicate with the database. Depending on the contents of your Isah License Server, choose one of the following options:
If your Isah License Server contains only one production database, stop the Isah License Server.
If your Isah License Server contains multiple production databases, delete the entry for the database you are migrating.
Make a backup of the database to migrate.
If applicable, disable database triggers on the database to migrate.
Stop the SQL Server Agent (in SSMS, right-click on SQL Server Agent and choose Stop).
Remove replication for the database (only used in some customization).
Start a command prompt as administrator in the directory that contains the migration tool and run the Migrate.bat program. The tool will show the required parameters and the location of the output. Information on the migration steps that are run, is available in Migration Steps.
If the output is ok, patch the database with the IsahDBPatcher.
If errors occur while running the migration, analyze the migration output and solve the problems. This requires database knowledge. Restoring the backup of the database and rerunning the migration is not a solution.
If applicable, enable database triggers on the migrated database.
If applicable, re-install replication.
Make a backup of the database.
Start the SQL Server Agent (in SSMS, right-click on SQL Server Agent and choose Start).
Start all windows services that communicate with the database. Depending on the action you performed in step 2, choose one of the following options:
If you stopped the Isah License Server, start the Isah License Server again.
If you deleted the entry for the database, add the entry again.
Start all web services that communicate with the database.
