1. In the Sybase section of the SSMA tool, click to open Views.
2. Select the check boxes of the custom views.
3. Right-click Views and choose Convert Schema.

   

Warning: Make sure you only select the custom views. You can find the list of customized views in the document ...\<My Documents>\Isah Migrationbox\<Project>\Output\List_Customizing.txt.

When the code migration has finished, add the views to the MS SQL database:

1. Expand Views in the MS SQL Server section at the bottom of the window.
2. Select the custom views.
3. Choose Synchronize with database.

   

   You will now see a window in which the action column should have a blue arrow pointing to the left (objects from 'Local Metadata' to 'Database').

   

   If you see a green arrow pointing in the other direction, double-click the icon. First a grey cross will appear; after that, a blue arrow appears, pointing in the correct direction.

1. In the Sybase section of the SSMA tool, place the cursor on Views and deselect it.
2. Navigate to the Procedures branch and select it.
3. Expand the Procedures branch.
4. Deselect the IP_gen_Log, IP_chk_IsahUserCode and IP_chk_UserCode procedures.
5. Make sure the Procedures branch is selected in the Sybase Metadata Explorer.
6. Choose Convert Schema (right-click or click the button). Convert Schema translates the Sybase object code saved on disk to the code for MS SQL Server objects. The MS SQL Server code is also saved to disk.

   At the bottom of the screen, a list of errors, warnings and information is displayed.

   

   To enable or disable a particular type of message, click the Errors, Warnings or Information tab. Procedures with at least one message are recognizable by a small red cross in the Sybase pane. When you click a message in the bottom pane, the files with the Sybase code and the MS SQL Server code are opened in the upper panes. You can find the location of the error by searching for the error ID (for example, S2SS0064) in the MS SQL Server code. Please note that a procedure can have the same error ID more than once. This way, you can solve the errors from within the SSMA tool. Because errors found in the code are marked in comments, you can add the code to the MS SQL Server database and then search for the 'S2SS' string.

   Please refer to Appendix B: SSMA Conversion Errors To Be Solved for a list of the SSMA errors, warnings and information messages and for pointers to solutions.

Note: Create a migration report before changing any code (see step 40).

The list of messages is deleted:

• when a new Convert Schema or Synchronize with database action is performed, or
• when the SSMA tool is exited.

However, you can also generate an error report which you can still access at a later stage:

• Click the Create Report button on the toolbar.

  

  A Report folder will now be created in the SSMA project directory. It contains a subfolder with a name showing the date and time the report was generated (<report_yyyy_mm_ddThh_mm_ss>). One of the items in this folder is the mainindex.html file. This html file allows you to view the migration information at any time.

  

Open mainindex.html. A browser window opens showing messages at the bottom. You will see an object name followed by the number of messages in that object.

• If you click a procedure, for instance a procedure with errors, the upper section will display the Sybase code on the left and the MS SQL code on the right.
• If you click a message in the MS SQL Server section, the corresponding statements are marked on both the Sybase side and the MS SQL Server side.

  

You cannot make any changes from within the browser. To make changes, you need to use the SSMA tool. Please refer to Appendix B: SSMA Conversion Errors To Be Solved for the various types of errors and for pointers to solutions.

1. Run Synchronize with database on the stored procedures on the MS SQL Server side. This may result in errors if the SSMA tool has chosen an incorrect translation or if the SSMA tool missed an SQL construction that should have been translated from ASE T-SQL to MSSQL T-SQL.
2. In the SSMA tool, open the MS SQL Server code of these objects one by one and try to add them to the database from within Management Studio. You will see more information about the exact nature of the errors. Solve these errors.

Example of a possible error: You have a stored procedure with a datetime parameter, but an integer is assigned as the default value to this parameter. Sybase compiles the procedure, but will return an error during run time if the parameter is not provided, as there is no implicit conversion from integer to datetime. MS SQL Server will return an error during the compilation time.

The problem with processing the custom triggers is that the triggers are dependent on their tables, but triggers must be selected at table level. Standard tables make it difficult to find the custom triggers. The selection must therefore be restricted somehow.

1. In the Sybase section of the SSMA tool, place the cursor on Tables and choose Advanced Object Selection.

   

   A window is displayed showing all table names.

2. Click the folder tree (hint text is 'Displayed Only Loaded Items') to display underlying indexes and triggers as well. The object icon indicates the object type.

   

3. Use the Filter field to restrict the objects displayed. The filter string cannot contain wildcards. A LIKE construct is used to match the string to the object names shown. For instance, if all custom triggers start with 'SG_', this method will help you to find the objects you want quickly.

   

4. Select individual objects or make a selection with SHIFT+click and CTRL+click.
5. Once you have selected the objects of your choice, press the spacebar to check or uncheck all selected objects in one go. Clicking the Check All Items or Uncheck All Items button has the same effect.

   

6. To migrate your selection:
   • click the Close button
   • right-click Tables on the left-hand side of the dialog
   • choose Convert Schema. Because the SSMA tool also attempts to migrate the tables corresponding to the triggers, you will see the following message:

   

   • Choose Skip All.

Run Synchronize with database on the triggers on the MS SQL Server side. This may result in errors if the SSMA tool has chosen an incorrect translation. Solve these errors.

Use the Scripts\Check_Import_MSSQL.sql script to check if all customizations are present. Any missing objects and tables with incorrect column definitions are reported. The result set shows missing objects, missing indexes and columns with incorrect column definitions. Do not forget to check the Output tab, since since the results of the import check are reported there.