1. If it is not yet installed, install the following software on the machine on which the Isah Migration Box has been installed:
   • Sybase Open Client
   • SQL Server Native Client.

   This software is required in order to establish a connection with the database servers.

   If the Isah Migration Box was installed on the same machine as the Sybase server, the Sybase Open Client is already installed. If the Isah Migration Box was installed on the same machine as the SQL Server, the SQL Server Native Client is already installed.

2. Install a free developer edition.
3. Choose ´All regions´ and agree to the license terms.
4. In the Isah Migration Box application menu, go to Project, Project Settings and configure the Dump Path. This is the folder that houses the supplied Sybase database dumps; the database server must be able to access it.
5. Setup the Sybase and MS SQL Server connections.

1. Install the supplied SSMA for Sybase 5.2, including the Extension Pack. Choose a 'Typical' installation for both installations. For the extension pack, deselect the Install Tester Database check box.
2. Check if the 'Sysdb' database has been created on the MS SQL Server. If it hasn't, the Extension Pack was not installed correctly. In this case, uninstall the Extension Pack, and then re-install it.

Note: If the Isah Migration Box was not installed on the same machine as the Microsoft SQL Server, you must also install the SSMA tool on the SQL Server.

1. Start SSMA. Make sure you choose the 32-bit version. The first time you start SSMA, you have to enter the path to the license file. The license file sybase-ssma.license can be found in the MigrationBox setup directory, subdirectory …\Software\SQL_Server_Migration_Assistant.
2. Choose Tools, Default Project Settings and choose the desired Migration Target Version: either SQL Server 2012 or SQL Server 2008.
3. Go to General, Conversion, System functions:

   INDEX_COL function: set to 'Convert function'

   INDEX_COLORDER function: set to 'Convert function'

1. Start SSMA. Make sure you choose the 32-bit version.
2. Choose Tools, Default Project Settings, Type mapping.
3. Edit the settings as follows:
   • char must be translated to 'nchar'
   • image must be translated to 'varbinary(max)'
   • text must be translated to 'nvarchar(max)'
   • varchar must be translated to 'nvarchar'
4. Click the Apply button in the Project Settings window.

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.