1. Click the Generate script button to generate the script MSSQL_Customizing_UDTs.sql.
2. Click the Run script button to run the generated script on the MS SQL Server conversion database, which will add the custom UDTs to the database.

Click the Run button to mark all UDTs in the code in the files. All code is now copied to new folders, the names of which contain the text 'UDTs_marked'.

Click the Run button to delete all custom triggers from the Sybase database.

Click the Run button to delete all custom procedures from the Sybase database.

All objects in the files will now be re-imported into the database:

1. Click the Run button to start the import process. Any errors are logged.
2. Check the log to see if there are any errors and if there are, solve them.

Run the Check_Import_ASE.sql script shown on the Sybase database to check for procedures or triggers that could not be created. The list contains the objects that could not be imported. If the list is empty, the process was successful.

A common reason for failure to create a stored procedure is that the CODE BEFORE and CODE AFTER blocks could not be created because the proper CAST format was not used in the procedure. If this is the case, create the procedure manually:

1. Open the script.
2. Create or correct the CODE BEFORE and CODE AFTER blocks manually.
3. Run the script on the database from within SQL Advantage. Use the code in the ASE_StoredProcs_UDTs_marked and ASE_Triggers_UDTs_marked folders.
4. Check if all objects are now present. Do not forget to check the Output tab, since missing objects are reported there.

Note: In MS SQL, the CODE BEFORE and CODE AFTER blocks are no longer needed; in new customizations, these blocks will be left out.

The SSMA tool does not support UDTs. The SSMA tool also fails to perform the type conversions 'char → nchar' and 'varchar → nvarchar' for columns. Because of this, the tables must be migrated with the help of a generated script before the SSMA tool is started. After this script has been run, the SSMA tool will read the MS SQL definition of these tables correctly.

1. Click the Generate script button to generate the Create_Customizing_Tables.sql script. The script that is generated starts with a header in which all custom indexes on standard tables are created.
2. Check the loaded MS SQL Server database to see if these indexes are still required. Some indexes may now be included in the standard version.

   The second header contains the scripts used for creating custom tables, including their primary key, indexes, defaults, rules and foreign keys. Defaults and rules on the MS SQL Server side have changed. Defaults are now 'column defaults'; rules are now 'check constraints'.

3. Scan the generated script for the words 'WARNING' and 'UNKNOWN'. Foreign keys in the customer database referring to another database are no longer created in MS SQL Server. MS SQL Server does not support cross database foreign keys. These foreign keys are marked with the word 'WARNING'.
4. If a cross database reference is intended, use triggers in MS SQL Server. Otherwise, rewrite the foreign key constraint so that it refers to a table in the same database.

   If the script cannot generate a name or code for a rule or default, the item will show 'UNKNOWN'. In this case, check the definition in the Sybase server and manually modify the script to ensure a corresponding rule or default is created in MS SQL Server.

   Please refer to the Example_defaults_rules.sql script for the naming conventions. The location of this script is %ProgramFiles(x86)%\Isah\Tools\Isah Migrationbox\Scripts\Example_defaults_rules.sql.

5. Run the generated script.

The SSMA tool cannot handle identity columns. For this reason, the identity columns will be reintroduced afterwards with the help of a generated script.

1. Click the Generate script button to generate the IdentityTables.sql script. This script is generated and saved automatically, and is used later.
2. Scan the generated script for the words 'WARNING' and 'UNKNOWN'. Foreign keys in the customer database referring to another database are no longer created in MS SQL Server. MS SQL Server does not support cross database foreign keys. These foreign keys are marked with the word 'WARNING'.
3. If a cross database reference is intended, use triggers in MS SQL Server. Otherwise, rewrite the foreign key constraint so that it refers to a table in the same database.

   If the script cannot generate a name or code for a rule or default, the item will show 'UNKNOWN'. In this case, check the definition in the Sybase server and manually modify the script to ensure a corresponding rule or default is created in MS SQL Server.

4. Please refer to the Example_defaults_rules.sql script for the naming conventions. The location of this script is %ProgramFiles(x86)%\Isah\Tools\Isah Migrationbox\Scripts\Example_defaults_rules.sql.