Dialect 2 Clients

Go Up to Understanding SQL Dialects

Dialect 2 is available only on the client side. It is intended for assessing possible problems in legacy metadata that is being migrated to dialect 3. To determine where the problem spots are when you migrate a database from dialect 1 to dialect 3, you extract the metadata from the database, set isql to dialect 2, and then run that metadata file through isql. isql issues warning whenever it encounters double quotes, DATE data types, or large exact numerics to alert you to places where you might need to change the metadata in order to make a successful migration to dialect 3.

To detect problem areas in the metadata of a database that you are migrating, extract the metadata and run it through a dialect 2 client, which will report all instances of transition features. For example:

isql -i v5metadata.sql

Do not assign dialect 2 to databases.