12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667 |
- <!--
- Licensed Materials - Property of IBM
- IBM Cognos Products: fmmd
- (C) Copyright IBM Corp. 2003, 2019
- US Government Users Restricted Rights - Use, duplication or disclosure
- restricted by GSA ADP Schedule Contract with IBM Corp.
- -->
- <Preferences xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../bme/prod/templates/TestFiles/Preferences.xsd">
- <!-- This setting controls the syntax of the Macro Editor -->
- <Section Name="UseTabbedSQLEditor">
- <Preference Name="value">TRUE</Preference>
- </Section>
- <Section Name="NewMacroSyntax">
- <Preference Name="value">TRUE</Preference>
- </Section>
- <!-- This setting controls how many views will be put in each publish transaction. This number can be raised to increase performance on machines with a lot of free RAM -->
- <Section Name="PublishOptions">
- <Preference Name="ModelViewChunkLimit">2000</Preference>
- <Preference Name="SetPolicyPackage">TRUE</Preference>
- </Section>
- <!-- This setting controls when the user will get prompted for prompt values-->
- <Section Name="AlwaysPromptOnTesting">
- <Preference Name="value">TRUE</Preference>
- </Section>
- <!-- The following section contains settings that pertain to behavior for the imports-->
- <Section Name="ModelImportOptions">
- <!-- This setting dictates how to treat a namespace or folder that is selected for import but whose name conflicts with that of an existing namespace or folder in the target model.
-
- If TRUE, then the namespace or folder will not be but its children will still be imported, but placed under the existing object in the target model, thus facilitating a "merge"-like operation. This behavior will always occur, superceding the option presented to the user to "Import and create a unique name" or "Do not import" whenever a duplicate name is detected, which still is enforced on other object types.
- If FALSE, then nothing speclal is done on conflicting namespaces or folders, and the "Import and create a unique name" or "Do not import" options apply to them as well.-->
- <Preference Name="MergeConflictingContainers">TRUE</Preference>
- <!-- The following setting controls whether or not to allow empty namespaces or folders to be imported into the target model.-->
- <Preference Name="AllowEmptyContainers">FALSE</Preference>
- </Section>
- <!-- This setting contains SQL preference information -->
- <Section Name="SQLPreference">
- <Preference Name="RestrictTheMaximumNumberOfRows">TRUE</Preference>
- <Preference Name="MaximumNumberOfRows">25</Preference>
- <Preference Name="ApplyRelevantDesignModeFilters">FALSE</Preference>
- <Preference Name="LevelOfDetail">5</Preference>
- </Section>
- <Section Name="ImportDatabaseSystemObjects">
- <Preference Name="value">FALSE</Preference>
- </Section>
- <Section Name="NagMessageXSL">
- <Preference Name="value">..\bin\NagMessageXForm.xsl</Preference>
- </Section>
- <Section Name="ModelDocXSL">
- <Preference Name="value"></Preference>
- </Section>
- <Section Name="DumpOptions">
- <Preference Name="RelmdResponses">FALSE</Preference>
- </Section>
- <Section Name="Statistics">
- <Preference Name="RowCountEnabled">FALSE</Preference>
- </Section>
- <Section Name="DynamicQueryMode">
- <Preference Name="SendRequestsToOlapXQE">TRUE</Preference>
- <Preference Name="UseLocalCacheXQE">FALSE</Preference>
- <Preference Name="NumberOfRequestRetries">10</Preference>
- </Section>
- </Preferences>
|