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. Load the supplied Convert45DB.dmp in Sybase into Convert45_<%DatabaseName%>. For example: Convert45_IsahDB. To do this, run the Create_ASE_Convert45DB.sql script.
2. Verify that the placeholders for the database name and the path to the dump have been replaced correctly. Make corrections if necessary.
3. Replace the placeholders. The <%Size%> placeholder can be calculated as set out below:
   • Run the 'exec sp_SpaceUsed T_FinJournalDetail' command on the database that is to be converted.
   • Take the number shown in the 'reserved' column. This is the number of KBs needed for T_FinJournalDetail.
   • Divide this number by 1024 to convert the number into MBs.
   • Add 256 MB to the result.
   • Round this number off upwards so you get a 'round' number of GBs. In this context, 'round' is a power of two (1024 MB, 2048 MB, 3072 MB, 4096 MB, etc.).
4. 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.

Example

sp_SpaceUsed indicates that 1,621,422 KB has been reserved.

1,621,422 KB / 1,024 ≈ 1,583.42 MB ≈ 1,584 MB

1,584 MB + 256 MB = 1,839 MB

Rounding off 1,839 MB results in 2,048 MB

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.

Note: To be able to do this, the Isah Database Management Tools (IDBMT) need to be installed on the Sybase server.

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.

1. Click the Generate script button to generate the Customizing_Permissions.sql script. The generated script will be shown.
2. Go to the heading 'These permissions might have to be changed'. These permissions concern the permissions directly assigned to a user. Check if they can remain unchanged or if they should be modified. In standard Isah, permissions are assigned to a role and roles are linked to users.

The generated script is saved automatically.

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

Click the Run script button to generate the Create_IDX_FinJournalDetail.sql script. The generated script is saved automatically.

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.

The script that was generated in step 12, Create_IDX_FinJournalDetail.sql, is displayed. Run this script.

The WipeLoginame.sql script is displayed. Run this script.

The DeleteAliases.sql script is displayed. Run this script.

In this step you generate a list containing all non-standard objects.

1. Click the Generate report button to generate the list. The list is also saved in the List_Customizing.txt file in the Output folder of the project folder.
2. Check the list and decide if these objects are customizations or if they can be deleted.
3. Delete any objects that do not need to be migrated and rename any objects that have to be renamed.

1. In MS SQL Server, create a database and restore the supplied empty Isah 4.5 database into this new database. You can use the script shown to load the database or you can use Management Studio.

   If you use the script, check if the placeholders for dump path, data path and log path have the correct values in the script. Correct them if necessary.

2. Replace the <%Size%> placeholder by the correct value for the data file size, which can be calculated as follows:
   • Take the size of the ASE .dmp file.
   • Add 30%.
   • Round off the result upwards to entire GBs and enter the result.
3. Run the script.
4. After restoring the database, set the compatibility level of the database to SQL Server 2012:
   • Right-click the database.
   • Choose Properties, Page Options.
   • In the drop down list Compatibility level, choose 'SQL Server 2012 (110)'.

Note: If you are migrating to SQL Server 2008 R2, setting the compatibility level is not necessary.

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.

Calculating the data file size: an example

Database dump = 27,217,191 KB

+30% = 27,217,191 KB × 1.3 = 35,382,348.3 KB

Rounded off to GB: 35,382,348.3 KB / (1,024 × 1,024) ≈ 33.74 GB → 34 GB

Note: The size must be specified in MBs: 34 × 1,024 = 34,816 MB

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

   The <%DatabaseName%> section must match the name of the SQL Server database that is to be converted exactly (for example, Convert45_IsahDB). In various scripts, this database name is appended to the Convert45_ string.

2. Restore the MSSQL Convert45DB backup into the newly created database.

   The backup is located in the migration folder, Dumps subfolder and is called MSSQL_Convert45DB.bak. If the backup folder is not on the database server, you have to move the backup to the database server. If you need to do this, the backup folder of the database server probably does not match the folder shown in the load script. Change the folder in the load script so it matches the backup folder.

3. After restoring the database, set the compatibility level of the database to SQL Server 2012:
   • Right-click the database.
   • Choose Properties, Page Options.
   • In the drop down list Compatibility level, choose 'SQL Server 2012 (110)'.

Note: If you are migrating to SQL Server 2008 R2, setting the compatibility level is not necessary.

Run the Populate Convert45DB ASE.sql script to populate the ASE conversion database on the database that is to be migrated.

1. Click the Generate script button to generate the script.
2. Click the Run script 1 button to run the generated script on the MS SQL Server conversion database. The Run script 1 button also generates a second script.
3. Click the Run script 2 button to run the second script on the MS SQL Server conversion database.