oledb.properties 2.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. # Licensed Materials - Property of IBM
  2. # IBM Cognos Products: OQP
  3. # (C) Copyright IBM Corp. 2005, 2019
  4. # US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM corp.
  5. #
  6. # OLAP Metadata for OLEDB providers.
  7. #
  8. # Indicates if we should be faking member keys. This is required for when we have no knowledge of the keys.
  9. olap.metadata.fakeMemberKey=true
  10. # Indicates if we should be skipping any property that ends in ".MEMBER_KEY". This is needed for Cubing Services,
  11. # since we get two MEMBER_KEY properties returned when the customer has modeled it, and we only need one! :)
  12. olap.metadata.skipDotMemberKey=false
  13. # Indicates if we should be forcing parent-child hierarchies to be treated as unbalanced.
  14. olap.metadata.forceParentChildToUnbalanced=false
  15. # Indicates if we should be forcing ragged hierarchies to be treated as unbalanced.
  16. olap.metadata.forceRaggedToUnbalanced=false
  17. # Indicates if we should be returning hierarchies as dimensions.
  18. olap.metadata.returnHierarchiesAsDimensions=false
  19. # Indicates if we should be using the level names to determine if a hierarchy is parent-child. For MSAS 2000 and
  20. # Cubing Services, if all the level names for a hierarchy start with "Level " and a number, then we consider it to
  21. # be a parent-child hierarchy.
  22. olap.metadata.determineParentChildByLevelNames=false
  23. # Indicates if we can use Member Unique Names for the Actions restrictions.
  24. # For MSAS 2005+, this is fine. For 2000, when retrieving the Dimension Actions, the
  25. # co-ordinate must be a HUN :). For Level Actions, it must be a LUN (not a MUN).
  26. olap.metadata.useMUNsForActionRestrictions=true
  27. # MDDS doesn't worry about sorting hierarchies for MS2005+.
  28. # In order to remain consistent the ODBO provider shouldn't either.
  29. olap.metadata.applyNewRankToHierarchies=false
  30. # Does this provider support Trusted Connections.
  31. olap.connection.supportsTrustedConnections=true
  32. # Does this provider support CAM Authentication (SSO).
  33. olap.connection.supportsCAMAuthentication=true
  34. # Can we use impersonation with the signon supplied?
  35. olap.connection.supportsUserImpersonate=true
  36. # Can we skip version validation?
  37. olap.connection.skipValidateVersions=false
  38. # Should we use tabular formatting?
  39. olap.data.useTabularFormatter=false