Click the Generate script button to generate the Create_IDXs.sql script with which all indexes will be created. The script is automatically saved for later use.

Run the Generate_Drop_IDXs.sql script shown on the MS SQL database.

The SEPA/IBAN conversion already performed during the test migration has to be undone. In Sybase, new data could have been added to tables containing bank account information. These new data should be properly converted as well. If you undo the SEPA/IBAN migration, applying the latest database patch will migrate all data.

Click the Run script button to run the Undo_SEPA_IBAN.sql script.

1. Start the SSMA tool and open the migration project created earlier.
2. In the Sybase section of the SSMA tool, select Tables. All tables are now selected.
3. Right-click Tables and choose Migrate Data.

   

4. Log onto the ASE server.

You now have to wait for about four to eight hours.

Following the data migration, create a report containing the results in the SSMA tool:

• Click the Save Report button and enter a file name and file location.

Change the Isah version number to the new format.

Click the Run button to check the data migration. For every table, the number of records in the Sybase database is compared with the number of records in the MS SQL database. Any differences are logged. A list of all tables and the number of records are saved in the TablesRecordCount.log file.

If any of the tables have not been migrated correctly, you can use the scripts in the Data_Repair folder to:

• disable the triggers and foreign keys (scripts 01 and 02)
• clear the failed tables (script 03)
• re-enable the foreign keys and triggers (scripts 04 and 05). The foreign keys and triggers must be enabled for the SSMA tool to work.

After this, use the SSMA tool to transfer the contents of the failed tables only.

Warning: Do not forget to modify the WHERE clause in script 03. Otherwise, all tables will be cleared.

Run the Save_ASE_Config.sql script.

Run the SaveIdentityTables.sql script that was generated in a previous step.

Run the Restore_TestConfig.sql script. The script may report the error “SQL Error: SQL Error Code: 50000 Not all foreign key constraints are trusted”. You can ignore this error for now.

Run the T_ProjectLineCostBudgetLog_After.sql script shown on the MS SQL database.

1. Click the Generate script button to generate the script to reintroduce identity columns into custom tables.
2. Click the Run script 1 button to run the generated script on the MS SQL Server database.
3. Click the Run script 2 button to re-create triggers on the custom tables with identity columns.

The Create_IDXs.sql script that was created earlier is shown. Run this script.

This step will repair the reports, permissions and scripts that depend on obsolete reports, program codes and scripts.

• Run the scripts Delete_Obsolete_ProgramParams.sql and Delete_Obsolete_Permissions.sql.

In the tables below, delete all references to obsolete reports from the listed columns.

Run the Validate FKs and Rules.sql script.

Problematic constraints will be displayed on the Output tab.

Should there be any constraints that cannot be validated, adjust the column values that are not supported by the foreign key or check constraint.

1. Navigate to the folder containing the MS SQL Server database patch.
2. Read the Update Guide and follow the instructions to apply the latest patch to the MS SQL Server database.

   For large databases, set the transaction log to ´Unrestricted File Growth´ and check the Enable Autogrowth checkbox: right-click on Database, Properties, Files, Log file.

   

   After applying the patch, you can shrink the log again.