Progress
DataServer for
Microsoft SQL Server
Guide


Naming Conventions

When planning for maximum transparency across Progress databases and MSS data sources, be sure to consider the restrictions that each places on naming data source objects when you perform a Progress-to-MSS conversion. Table 2–2 describes these restrictions, and the notes that follow it discuss how the DataServer resolves differences between Progress and SQL Server™ naming conventions.

Table 2–2: Database Naming Restrictions

Category

Progress
SQL Server™
Alphanumeric characters
A–Z or a–z
0–9
All alphanumeric characters from the character set that you defined for your SQL Server™.
Special characters
Allows $, &, #, %, –, and _1
Allows @, $, #, _, ¥, and £2
Initial character
Alphabetic only
Alphabetic only
Maximum length of object name
32 characters
24 characters3
Keywords
Not allowed4
Not allowed4
Unique table names
Required5
Required6
  1. Although Progress allows you to use the ampersand (&) in database-object names, the Progress ADE tools use this character internally to denote preprocessor directives.
  2. When the DataServer encounters characters not supported by Progress in a table, index, or field name, it converts them to underscores ( _ ) in the schema holder. For example, the data source table name emp@status becomes emp_status in the schema holder. If the unsupported character is at the beginning of an object name, the DataServer substitutes a lowercase z. Also, the DataServer strips @ symbols from stored procedure parameter names.
  3. Object names are limited to 32 characters. When you use the Progress-to-MSS utility to perform a database conversion, however, the utility truncates object names to 24 characters in order to accommodate the suffix characters that it appends when it finds nonunique names, reused Progress keywords, array fields, sequences, triggers, and so forth. If you intend to use the Progress-to-MSS utility, be sure to limit object names to 24 characters to accommodate this name resolution during conversion.
  4. Progress and SQL Server™ databases contain restrictions against using keywords as database object names. If a data source object name consists of a Progress keyword, the DataServer appends an underscore character ( _ ) to the name. For example, an object named “each” becomes “each_”.
  5. SQL Server™ qualifies nonunique table names to make them unique (see your data source documentation for details); however, Progress still regards these qualified names as nonunique. The DataServer resolves nonunique table names for you as follows: when Progress encounters matching table names while creating or updating a schema holder, it names the second and subsequent tables table-1, table-2, etc. For example, if Progress encounters a table named lee.employee (the employee table owned by the user lee) that is the second instance of the name in the data source, it names the corresponding table in the schema holder employee-1.
    NOTE: When resolving naming conventions, the DataServer can append up to three characters to an object name: two in the case of a nonunique name and one in the case of a Progress keyword. Therefore, you should limit your object names to 29 characters so that you do not exceed the Progress 32-character limit for object names in the schema holder.
  6. SQL Server™ allows you to qualify an object name by adding the following:
    - the database name
    - the owner’s name
    - (for columns) the table name


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095