Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

> ## gsc_deploy_dataset table — gscdd

> This table defines the sets of data that must be deployed to end-user sites and migrated to different workspace databases. Usually it is static data that must be deployed. This table and its child table, `gsc_dataset_entity`, identify which pieces of data are dependent on each other and must be deployed as a set. For example, in order to deploy menu items, the objects on the menu item also must be deployed.

> This table and its child table, `gsc_dataset_entity`, also define the data set for deployment of logical objects managed by the source code management tool, such as the `ryc_smartobject` and related tables.

> To deploy and load the data, XML files are generated for the data set. The data set always has a main table and all the related tables that must be deployed with it, together with the appropriate join information. Example data sets could be for OpenEdge SmartObjects™, menus, and objects. Most data tables could be defined as separate data sets that include a parent data set. The parent data set includes whichever data sets must be deployed together.

> When automatically generating triggers from ERwin, an entity-level UDP (DeployData) indicates whether trigger code is generated for the static tables to support data deployment. A flag, `deploy_data`, also exists in the `entity_mnemonic` table for the same purpose.

> Table 3–5 lists the table’s FLA, fields, and foreign keys.

> Table 3–5: gsc_deploy_dataset table information
> Table FLA | Fields (data type) | Foreign keys
> --- | --- | ---
> gscdd | deploy_dataset_obj (Decimal) dataset_code (Character) dataset_description (Character) disable_ri (Logical) source_code_data (Logical) deploy_full_data (Logical) xml_generation_procedure (Character) default_ado_filename (Character) deploy_additions_only (Logical) enable_data_versioning (Logical) deletion_dataset (Logical) | deploy_dataset_obj

> Table 3–6 gives details of the table’s indexes.

> Table 3–6: gsc_deploy_dataset index information
> Index name | Elements | Type
> --- | --- | ---
> XPKgsc_deploy_dataset | deploy_dataset_obj | Primary Unique
> XAK1gsc_deploy_dataset | dataset_code | Unique
> XIE1gsc_deploy_dataset | dataset_description | Nonunique
> XIE2gsc_deploy_dataset | source_code_data | Nonunique

> For customer sites that receive a data set deployment, the last deployment loaded for this data set is recorded on this table. This helps identify the version of the static data in a particular database.

> A customer should not modify or deploy from the data sets sent by the application provider. Customers should create their own data sets containing the same tables and deploy from these data sets. A data set deployment includes an XML file registered as part of the deployment. Customers can use that XML file for their databases and any other databases or sites to which they want to pass the data.

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