Property |
Description | ||||||
---|---|---|---|---|---|---|---|
Table |
Name of the table in the data model. | ||||||
Usage type |
The table's usage type provides the basis for reports and the selection of tasks for daily maintenance. Permitted values are:
| ||||||
Display name (singular) |
Display name for a single record in the table. Translate the given text using the button. | ||||||
Display name (plural) |
Displays table name The display name is used, for example, to identify the table in a database search or for error output. Translate the given text using the button. | ||||||
Display template |
The display template is used to specify the form in which objects will be represented, for example in the administration tool result list or in reports. Translate the given text using the button.For more information, see Display template for displaying a list. NOTE: You do not need to enter a display template for many-to-many tables. For these tables, the viDB.DLL forms the display template from the foreign keys. | ||||||
Display template (long) |
Additional display template for individual tables containing the object's full name. | ||||||
Hierarchy path |
Enter the foreign key columns here that should be used as a basis for displaying tables hierarchically, for example, on assignment forms. For more information, see Hierarchical display of data on assignment forms. Example: An Active Directory user account (ADSAccount table) is typically displayed on an assignment form below its Active Directory container (UID_ADSContainer column). The Active Directory container (ADSContainer table) is, on the other hand, displayed underneath its Active Directory domain (UID_ADSDomain column). The path for the hierarchy structure is entered as follows:
An alternative list for objects that do not have values in all foreign key columns can be given after a pipe (|). Example: (UID_ADSContainer,UID_ADSDomain|UID_ADSDomain) | ||||||
Remarks |
Text field for additional explanation. | ||||||
Cache information |
Loading behavior for tables in the Designer. This data is only required for system tables. Cache information for a table is composed of the sort order and loading behavior. Permitted values are:
| ||||||
Disabled by preprocessor |
(DialogTable.IsDeactivatedByPreProcessor) If a table is disabled by a preprocessor condition, the option is set by the Database Compiler. For more information, see Conditional compilation using preprocessor conditions. | ||||||
Preprocessor condition |
You can add preprocessor conditions to tables. The table is therefore only available together with its columns when the preprocessor condition is fulfilled. For more information, see Conditional compilation using preprocessor conditions. | ||||||
Deferred deletion [days] |
Delete operations are deferred (0 = delete immediately, other: delete after given number of days). | ||||||
Icon |
Icon representing the table in the administration tool interface. | ||||||
Background color |
Color used to display the control for this table in the schema overview. | ||||||
Proxy view |
Reference to database view, type Proxy, which uses the table content. Example: The database view UNSRoot is used to map the ADSDomain and LDAPDomain tables in the Unified Namespace. | ||||||
Extensions to proxy view |
List of columns as SQL text. These are used in the database view's SELECT statement, which selected under Proxy view. For example, use the extensions to the proxy view if columns are doubly mapped or if additional proxy view need to be filled. Example: The view UNSRoot expects the target system type as input in the UID_DPRNameSpace column. This column is not in the ADSDomain and LDAPDomain tables. The proxy view extension is defined as follows:
| ||||||
Logical disk store |
The table's logical disk store. Associated tables are grouped together in logical disk stores. In the default installation, logical disk stores are predefined for the table in each module of One Identity Manager and the system tables. You cannot change the assignments. You can create your own logical disk storage for grouping custom tables. Supporting file groups | ||||||
Scope hierarchy |
Comma delimited list of all foreign key columns required for displaying objects in the scope hierarchy in the Synchronization Editor. List of all columns that lead to tables made available by the parent object. | ||||||
Export for SPML schema |
This option determines whether the table should be exported for the SPML schema. For more information, see Preparing the One Identity Manager schema for export to the SPML schema. | ||||||
Many-to-many table |
Label for assignment tables (many-to-many tables). Assignment tables are tables used to create relations between two other tables. For more information, see Table types and default columns in the One Identity Manager data model. | ||||||
Many-to-all table |
Marks assignment tables, which have a dynamic foreign key as partner. For more information, see Table types and default columns in the One Identity Manager data model. | ||||||
No DB Transport |
Tables labeled with this option cannot be excluded from a custom configuration package. These tables are excluded from data transport. | ||||||
Assign by event |
Specifies how assignments and deletions are handled in tables. This option only applies to assignment tables (many-to-many tables) in the application data model.
| ||||||
Retain in memory |
Specifies whether the table contents for the data connection can be buffered. The threshold is defined in the Common | ResidentTableLimit configuration parameter. | ||||||
Module GUID permitted |
Specifies whether a primary key with a Globally Unique Identifier module (GUID module) is permitted for an object. For more information, see Working with a globally unique identifier module. | ||||||
Module GUID required |
Specifies whether a primary key with a Globally Unique Identifier module (GUID module) is required for an object. For more information, see Working with a globally unique identifier module. | ||||||
Type |
Table type. For more information, see Table types in One Identity Manager. | ||||||
Base table |
Only for database views: Reference to base tables that a view is based on. | ||||||
Condition for view definition |
Only for database views: Limiting condition for creating the database view as WHERE clause for database queries. | ||||||
Insert values |
Specify default settings for a column that is assigned when a new data set is added. The values are entered in VB.Net syntax. | ||||||
Selection script |
Only for database views: Selection script as VB.Net expression to determine at runtime, whether the object passed belongs to this database view. | ||||||
Script (OnLoaded) |
Script in VB.Net syntax that is run after the object is loaded. For more information, see Table scripts. | ||||||
Script (OnSaving) |
Script in VB.Net syntax that is run before the object is saved. For more information, see Table scripts. | ||||||
Script (OnSaved) |
Script in VB.Net syntax that is run after the object is saved. For more information, see Table scripts. | ||||||
Script (OnDiscarding) |
Script in VB.Net syntax that is run before the object is discarded. For more information, see Table scripts. | ||||||
Script (OnDiscarded) |
Script in VB.Net syntax that is run after the object is discarded. For more information, see Table scripts. | ||||||
Number of rows |
Number of rows in the table The number of rows in the table is determined once a day by maintenance tasks. The data material can help to plan capacities and maintenance work on the database. | ||||||
Basic record lengths |
Maximum length of the data record with (clustered) main indexes. Only the reference is saved for LOBs. The LOB content itself is stored in the HEAP. The basic record length is determined once a day by maintenance tasks. The data material can help to plan capacities and maintenance work on the database. | ||||||
Table size |
The size of the table in MB. The size of the table in the database is determined once a day by maintenance tasks. The data material can help to plan capacities and maintenance work on the database. | ||||||
Condition for transport |
Condition for selecting transportable objects. An empty condition means that all object are transferred. | ||||||
Layout information |
(Only for internal use) Information about the layout in the Designer. | ||||||
Primary key 1 |
(Only for internal use) Name of the table's first primary key column. The sort order of primary key 1 and primary key 2 corresponds to the physical order in the schema. | ||||||
Primary key 2 |
(Only for internal use) Name of the table's second primary key column. The sort order of primary key 1 and primary key 2 corresponds to the physical order in the schema. |