Catalog
The root container of an OLAP schema that defines a complete analytical database. A Catalog represents a logical grouping of related cubes, dimensions, and data sources that together form a cohesive analytical model for a specific business domain or application. It serves as the top-level entry point for OLAP connections and contains all the metadata necessary to perform multidimensional analysis. The Catalog manages shared resources like dimension hierarchies, access roles, parameters, and database schema references, ensuring consistency and reusability across all contained analytical objects. In XMLA terms, this corresponds to a database or catalog that clients can connect to and browse.
Extends
- AbstractElement 🔗
Attributes
| Name | Id | Type | Lower | Upper |
|---|---|---|---|---|
| measuresDimensionName | false | EString | 0 | 1 |
| Optional custom name for the measures dimension that appears in MDX queries and XMLA metadata. By default, the measures dimension is named 'Measures', but this can be customized for localization or business terminology preferences. The measures dimension is a special system dimension that contains all the measures (metrics) available for analysis in each cube. This name appears in MDX syntax like [CustomMeasuresName].[Sales Amount] and in client tool dimension lists. | ||||
References
| Name | Type | Lower | Upper | Containment |
|---|---|---|---|---|
| parameters | Parameter🔗 | 0 | ∞ | true |
| Collection of schema-level parameters that provide dynamic behavior and configuration within the schema. Parameters enable runtime customization of schema elements, user-specific settings, and conditional logic in calculations. These parameters are available throughout the schema for use in calculated members, named sets, security expressions, and custom formatting. Common uses include date ranges for time intelligence, user preferences, locale settings, and business rule toggles. | ||||
| cubes | Cube🔗 | 1 | ∞ | false |
| Collection of cubes (both physical and virtual) that define the analytical content available in this catalog. Each cube represents a specific analytical perspective on the business data, containing measures for analysis and dimensions for slicing and dicing. Physical cubes map directly to fact tables and provide the foundation for analysis, while virtual cubes combine multiple physical cubes to create unified analytical views. While not strictly required, at least one cube is typically defined to provide analytical functionality. | ||||
| namedSets | NamedSet🔗 | 0 | ∞ | false |
| Collection of global named sets that define reusable member collections available across all cubes in the catalog. Named sets provide a way to define commonly used member groupings (like 'Top 10 Products', 'Current Quarter', or 'Key Customers') that can be referenced in MDX queries, calculated members, and reporting applications. These catalog-level named sets are shared across all cubes and provide consistency for common analytical concepts. | ||||
| accessRoles | AccessRole🔗 | 0 | ∞ | false |
| Collection of security roles that define access control policies for the schema and its contents. Each role specifies what cubes, dimensions, hierarchies, levels, and members a user or group can access, along with the specific permissions (read, write, drill-through) for each resource. Roles can be combined to create complex security scenarios and support both broad organizational permissions and fine-grained data restrictions. These roles are enforced by the OLAP engine during query execution and metadata discovery. | ||||
| defaultAccessRole | AccessRole🔗 | 0 | 1 | false |
| Reference to the access role that should be applied by default when users connect without explicit role assignment. This provides a baseline security policy for the schema, typically configured to allow basic read access to public data while restricting sensitive information. If not specified, Daanse does not assign a built-in default role, and access will be denied unless a role is explicitly provided. This setting is particularly useful for public reporting scenarios, shared dashboards, or development environments where default read access is desirable. | ||||
| dbschemas | DatabaseSchema🔗 | 0 | ∞ | false |
| Collection of database schemas that define the physical data model underlying this catalog. Each DatabaseSchema represents a logical grouping of tables, views, and columns from one or more physical databases. The catalog can integrate data from multiple database schemas, enabling cross-database analysis and federated OLAP scenarios. These schemas provide the foundation for all cube queries and define the available tables and columns for fact tables, dimension tables, and lookup tables. | ||||