DEPLOYMENT_PROJECTIONS
Contains information about projections created and dropped during the design. Each row contains information about a different projection. Database Designer populates this table after the design is deployed.
Column Name | Column Type | Description |
---|---|---|
deployment_id |
INTEGER | Unique ID that Database Designer assigned to the deployment. |
deployment_projection_id |
INTEGER | Unique ID that Database Designer assigned to the output projection. |
design_name |
VARCHAR | Name of the design being deployed. |
deployment_projection_name |
VARCHAR | Name that Database Designer assigned to the projection. |
anchor_table_schema |
VARCHAR |
Name of the schema that contains the table the projection is based on. If the schema belongs to a non-default namespace in an Eon Mode database, the schema name is front-qualified with the name of the schema's namespace. For example, |
anchor_table_name |
VARCHAR | Name of the table the projection is based on. |
deployment_operation |
VARCHAR | Action being taken on the projection, for example, add or drop. |
deployment_projection_type |
VARCHAR |
Indicates whether Database Designer has proposed new projections for this design (DBD) or is using the existing catalog design (CATALOG). The REENCODED suffix indicates that the projection sort order and segmentation are the same, but the projection columns have new encodings:
|
deploy_weight |
INTEGER | Weight of this projection in creating the design. This field is always 0 for projections that have been dropped. |
estimated_size_on_disk |
INTEGER | Approximate size of the projection on disk, in MB. |