1. Create a backup of the Sybase database and load it into a migration database.
2. Enable the 'select into' option. Use the Select_Into.sql script to do this.

Warning: The Sybase database and the MS SQL database must have the same name later on. Choose the name with care.

1. In ASE Server, create a Convert45_<%DatabaseName%>.

   <%DatabaseName%> must match the name of the customer database exactly; for example, Convert45_IsahDB. In various scripts, this database name is appended to the Convert45_ string.

2. Load the dump of the ASE Convert45DB back-up that was made after the test migration into the newly created database. It is important to use the dump that was created after the test migration, because it contains a table with all customizations. This table is consulted by a script in a later step. You can use the script in Create_ASE_Convert45DB.sql as a template.
3. Enable the 'Select into' option for the convert database. You can do this by running the Select_Into_Convert.sql script. This script is run on the database that is to be converted.

Run the latest Isah 4.0 patch to the database you want to migrate. You can download the latest Isah 4.0 version from the Isah Supportsite.

The column order in ASE Server must match the column order in MS SQL Server exactly. Run the script ColumnOrderMismatch.sql to perform this check.

In the MS SQL Server database, obsolete columns in T_IsahTable and T_ProgramGrp will have been dropped during the test migration. These missing columns will not cause a problem. It is therefore safe to ignore the warnings about 'T_IsahTable.LastUpdatedBy' and 'T_ProgramGrp.IsahInd'.

Any other deviation between the Sybase ASE table structure and the MS SQL Server table structure needs to be solved before the data can be migrated.

Run the Update_VersionNr.sql script to set the correct version number for the migration.

Run the 4_5_00_62 patch. Run RunDBUpgrade.cmd from the ASE_Database_Patches\90_DBPatch_4_5 subfolder. All standard Isah 4.0 objects (except for tables and views) are now deleted.

In MS SQL Server, create a backup of the database used for the test migration and restore it into the new production database.

Warning: The Sybase database and the MS SQL database must have the same name later on. Please make sure you use the same name you used for the Sybase database.

1. In MS SQL Server, create a Convert45_<%DatabaseName%>.

   <%DatabaseName%> must match the name of the customer database exactly; for example, Convert45_IsahDB. In various scripts, this database name is appended to the Convert45_ string.

2. Restore the MSSQL Convert45DB back-up that was made after the test migration into the newly created database. It is important to use the back-up that was created after the test migration, because it contains a table with all customizations. This table is consulted by a script in a later step.

Run the Save_TestConfig.sql script to save the setup made during the test migration.

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

1. Click the Extract trigger code button to save the trigger code.
2. Click the Extract identity tables button to generate the SaveIdentityTables.sql and RemoveIdentityColumns.sql scripts. These scripts are saved automatically.
3. Click the Remove identity columns button to run the RemoveIdentityColumns.sql script on the MS SQL Server database. The SaveIdentityTables.sql script will be used later.

1. Click the Generate script button to generate the script to clear all tables.
2. Click the Run script button to run the generated script on the MS SQL Server database.

If insufficient memory is available for the SSMA tool because the ASE server or the MS SQL server has allocated all RAM, the data migration process will be very slow. For instance, on an 8GB server you need to assign a maximum of 3 GB to ASE and a maximum of 2 GB to MS SQL Server. The OS also uses 1 GB, leaving 2 GB for the SSMA tool. On a 64-bit system, Sybase can allocate up to 4 GB. If MS SQL Server is not restricted, the server will use all available RAM.

MS SQL Server

1. From Management Studio, right-click the server and choose Properties.

   

2. In the Maximum server memory (in MB) field under the Memory item, type '2048' (for example).

   

Sybase

1. Stop the Sybase SQLServer _ <ServerName> Sybase service.
2. In the Sybase directory, open the <ServerName>.cfg file.
3. Look for max memory. It shows the number of 2 KB reserved pages (2,000,000 pages of 2 KB is 4 GB). If you lower this number, you may also have to restrict the default data cache.
4. Restart the Sybase service.