1.1 Before You Begin

In order to perform the production migration, you require the same software that is needed for the test migration. For the purpose of this step-by-step description, we therefore assume that the following software has been installed:

• Isah Migration Box
• SSMA tool
• Sybase Open Client
• SQL Server Native Client.

If this software has not been installed, it should be installed (again). Refer to the test migration steps for more information.

On the Sybase side, no new customizations may be present or may have been introduced in the time between the test migration and the production migration.

Back-ups of the ASE and MS SQL Server conversion databases made after the test migration must be available. Also, there should be a back-up of the Isah database made after the test migration, containing all code repairs.

The setup of the following tables is restored in the test environment. This means that any changes to the data in these tables in the Sybase ASE database will be lost during the production migration.

• T_ReportMain
• T_ReportMainML
• T_ReportSort
• T_ReportSortML
• T_ReportSpecialLayout
• T_ReportSpecialLayoutML
• T_ReportSelection
• T_ReportSelectionParam
• T_ReportSelectionParamML
• T_PrinterType
• T_SqlQuery
• T_Dataset
• T_DatasetLink
• T_Datamodule
• T_IndexDef
• T_IndexDefField
• T_ScriptList
• T_ScriptListML
• T_ScriptListGrp
• T_ScriptListGrpML
• T_MenuListMain
• T_MenuListDetail
• T_MenuListDetailML
• T_ProgramMenuList
• T_ProgramDataPresets
• T_ProgramDataPresetsML
• T_Program
• T_ProgramGrp
• T_UserPermission
• T_UserGrp
• T_UserGrpPermission
• T_UserFunction
• T_DossierStatusRange
• T_DossierStatusRangeUserGrp
• T_ProdStatusRange
• T_ProdStatusRangeUserGrp
• T_PurStatusRange
• T_PurStatusRangeUserGrp
• T_Logo
• T_DBVersion
• T_DBUpgrade