SSMA Tester Report Shows 0 Equivalent Tables in Migration from Sybase to MS SQL

Question

The SSMA Tester results for migrating Sybase to MS SQL indicate "equivalent tables" as 0. SSMA Tester results shows success.

What could be the reason for this outcome?

The table comparison was set to "Full" in SSMA Tester, but the result remains unchanged.

A simple "Students" table was tested, containing 5 records: StudentId (Primary Key), StudentName, but the message indicating equivalent tables remains at 0.

Verification steps taken include:

• The database character sets are equivalent: Sybase uses ISO-8859-1 Binary Sorting, while MS SQL uses Latin_General1_100_BIN2.
• Data types match in both MS SQL and Sybase.
• The database names were made the same.
• The latest SSMA version, along with the Extension pack, was installed.

Any insights on why this issue persists would be appreciated.

Answer 1

There could be several reasons why the SSMA Tester reports "0 equivalent tables" despite having taken the verification steps you mentioned. Here are some potential issues to consider:

1. Data Comparison Settings: Ensure that the comparison settings for the columns are correctly configured. For instance, if "Ignore Strings Case" is set to True, it could affect the comparison results if there are case differences in the data.
2. Data Type Compatibility: Even though you mentioned that the data types match, it's essential to verify that the specific attributes (like precision and scale for numeric types) are also aligned. Any discrepancies here can lead to failed comparisons.
3. Row-Level Data: Since you are using the "Full" comparison mode, ensure that the actual data in the "Students" table matches exactly between Sybase and MS SQL. Any differences in the data, even in whitespace or casing, could result in a failure to recognize equivalent tables.
4. SSMA Tester Limitations: The SSMA Tester has certain limitations, such as not supporting parallel execution by different users on the same source or target server. Ensure that no other processes are interfering with the testing.
5. Execution Context: If the SSMA Tester is run in a context where the source schema and data are modified, it may lead to unexpected results. Always ensure that the testing environment is stable and that no other operations are affecting the data during the test.
6. Error Messages: Check if there are any error messages or warnings in the SSMA Tester report that might indicate issues with specific objects or configurations.

If you've verified all these aspects and the issue persists, it might be beneficial to consult the SSMA documentation or support for further assistance.

---

References:

• Testing Migrated Database Objects (SybaseToSQL)
• Viewing Test Case Reports (SybaseToSQL)