Accessing the dynamic sourcing VLDB properties for a project

Various VLDB properties control whether dynamic sourcing is enabled for reports, attributes, metrics, and aggregate tables. Defining these VLDB properties at the project level allows you to define a default dynamic sourcing behavior for these objects. While this defines the default behavior, any modifications to the VLDB properties for a specific report, attribute, or metric take precedence over the project-wide default.

For information on how to access the dynamic sourcing for individual reports, Intelligent Cubes, attributes, metrics, and aggregate tables, refer to the listed topics in About configuring dynamic sourcing.

The steps below show you how to access the dynamic sourcing VLDB properties for a project to define project-wide defaults, and includes information on how to set VLDB properties for each object type. The dynamic sourcing VLDB properties that you can define for a project are as follows:

Enable Dynamic Sourcing for Report: You can enable dynamic sourcing for a report so that active Intelligent Cubes (that are also enabled for dynamic sourcing) are checked to see if the report can retrieve its data from an Intelligent Cube. For additional information on this VLDB property and how to define it for individual reports, see Enabling or disabling dynamic sourcing for reports.
Attribute Validation: Attributes are available for dynamic sourcing by default. However, if attributes use inner joins, which is more common, you should verify that the attribute data can be correctly represented through dynamic sourcing. If some attributes fit these scenarios, you can disable dynamic sourcing when these attributes are used in reports and Intelligent Cubes. For additional information on this VLDB property and how to define it for individual attributes, see Disabling dynamic sourcing for attributes.
Metric Validation: Metrics are available for dynamic sourcing by default. However, if metrics use inner joins, which is more common, you should verify that the metric data can be correctly represented through dynamic sourcing. If the fact table that stores data for metrics includes NULL values for metric data, this can cause metrics that use inner joins to return incorrect data when dynamic sourcing is used. If some metrics do fit this scenario, you can disable dynamic sourcing when these metrics are used in reports and Intelligent Cubes. For additional information on this VLDB property and how to define it for individual metrics, see Disabling dynamic sourcing for metrics.
Aggregate Table Validation: Reports that use aggregate tables are available for dynamic sourcing by default. However, if the aggregate tables use an aggregation other than Sum, or there is different data between aggregate tables and other tables in the data warehouse, this can cause aggregate tables to return incorrect data when dynamic sourcing is used. If some aggregate tables do fit these scenarios, you can disable dynamic sourcing when these aggregate tables are used in reports and Intelligent Cube. For additional information on this VLDB property and how to enable or disable this feature for an individual report that uses an aggregate table see: Disabling dynamic sourcing for aggregate tables.
String Comparison Behavior: You can define attributes to either allow filter qualifications to be completed without enforcing case sensitivity, or to disable dynamic sourcing if these types of filters are used on attributes. You can configure this dynamic sourcing behavior for attributes by modifying the String Comparison Behavior VLDB property, as described in Supporting filtering on attributes for dynamic sourcing.

To define dynamic sourcing VLDB properties for a project

In MicroStrategy Developer, log in to a project source with a user account with administrative privileges.
Right-click a project and select Project Configuration. The Project Configuration Editor opens.
In the Categories list, expand Project definition, and then select Advanced.
In the Analytical Engine VLDB Properties area, click Configure. The VLDB Properties Editor opens.
From the Tools menu, select the Show AdvancedSettings option if it is not already selected.
In the VLDB Settings list, expand Dynamic Sourcing. The dynamic sourcing VLDB properties are displayed. To modify the default setting, select a VLDB property and then clear the Use default inherited value check box.
Click Save and Close to save your changes to the VLDB properties and close the VLDB Properties Editor.
Click OK to save your changes to the project and close the Project Configuration Editor.