Kbase P61404: How does the ProtoXXX DataServer utility work across all the
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/01/2004 |
|
Status: Unverified
GOAL:
How does the ProtoXXX DataServer utility work across all the supported foreign databases?
GOAL:
What are the steps involved in the protoora or in the protomss or in the protoodb process?
GOAL:
How Does the protoora works?
GOAL:
How Does the protomss works?
GOAL:
How Does the protoodb works?
FACT(s) (Environment):
DataServers
FIX:
All the steps performed during the ProtoXXX process are presented below:
1. Creates an empty schema holder
2. Reads the Progress database and generates a .SQL script. This script represents the Progress schema that will be created within the foreign data source.
The script will generate the correct data-types and names for the foreign data source. Objects name in the foreign data sources are limited by the DataServer. Because of the limitation table and field names in different foreign databases could be different.
The DataServer truncates tables and fields names to 24 characters for the most of the foreign sources except for the following:
Foreign Data Source Name -----------Length of table/field name
Oracle ---------------------------------------- 26
Informix -------------------------------------- 18
DB2 ------------------------------------------- 18
Microsoft Access ------------------------------ 33
Microsoft SQL Server ------------------------- 128 (in 9.1C or higher)
The difference in size is because it may have to append characters for shadow columns, arrays or indexes, and reserved words, such as Order (Progress allows order key word for a table or field name), etc. The DataServer also converts other incompatible characters such as hyphens (-), percent (%) and ampersand (&) to underscores (_).
3. The DataServer connects to the empty schema holder, reads the .SQL script and sends the corresponding SQL to create the objects within the foreign database.
4. The objects are pulled from the foreign data source into the schema holder.
5. The adjust schema is done. During this stage, the foreign schema image is compared to the original Progress schema. This is when the mapping between the objects within the foreign database and Progress is established.
6. If "Load Data" is selected, this occurs after the adjust schema is done.