Keeping Measure Indexes Under Control

Out of the box, the BI Gateway Runtime creates each Measure with a set of Indexes. Three Indexes for Date/Time columns and one Index per associated Dimension. While the purpose of these indexes is to speed up the presentation software in reading the data, having these indexes is not always preferred because they can use a lot of hard disk space and reduce the time to produce the data during the backfill process.

The KeepNonClusteredMeasureIndexesDisabled setting available in the EMIRuntimeConfigurator.xml file controls whether these additional indexes are enabled or disabled. If the setting is set to False (the default), then the indexes are created and enabled. If the setting is set to True, then the indexes are still created but disabled before any data is entered into the Measure. Note that both settings will still create the index. This will give you the opportunity to enable them in SQL Server. For instance, you can enable them once the backfill is done using SQL Server Management Studio by navigating to the Table's Indexes node and right-clicking, then choosing "Rebuild". Alternatively you can do this through a SQL Script.

To configure the KeepNonClusteredMeasureIndexesDisabled setting

1. Open the EMIRuntimeConfigurator.xml file in a notepad editor from the BI Gateway Installation Bin directory. For example: C:\Program Files (x86)\Wonderware\Intelligence\Bin.

2. Edit the XML file and update the following information, which is set to False by default:

   <KeepNonClusteredMeasureIndexesDisabled>False</KeepNonClusteredMeasureIndexesDisabled>

3. Save and close the file.

4. Restart the Intelligence Runtime service in order for the KeepNonClusteredMeasureIndexesDisabled setting to take effect after changing this setting in the EMIRuntimeConfigurator.xml file.