If you are using custom applications or business intelligence tools, you may want to collect statistics on Data Dictionary tables, because these applications and tools often query the Data Dictionary for validation or information checks in the background.
Components within Vantage use internal express requests that are optimized single-AMP queries. Statistics on Data Dictionary tables do not benefit these internal activities but benefit SQL submitted directly by a user or an application.
The value of collecting statistics on dictionary tables depends on the frequency and complexity of the queries that access the dictionary tables, the amount of resource the queries use, and how long the queries run on your platform. Using DBQL can help determine the benefit, but requires the DBC logon to collect against Data Dictionary tables. To decide whether to collect statistics on Data Dictionary tables, examine the DBQL output to determine if your applications use significant resources to access the Data Dictionary.
- DBC.AccessRights
- DBC.DBase
- DBC.Indexes
- DBC.Owners
- DBC.Profiles
- DBC.Roles
- DBC.RoleGrants
- DBC.TVFields
- DBC.TVM
- DBC.UDFInfo
- DBC.Acctg
- DBC.ChangedRowJournal
- DBC.DatabaseSpace
- DBC.LocalSessionStatusTable
- DBC.LocalTransactionStatusTable
- DBC.OrdSysChngTable
- DBC.RecoveryLockTable
- DBC.RecoveryPJTable
- DBC.SavedTransactionStatus
- DBC.SysRcvStatJournal
- DBC.TransientJournal
- DBC.UtilityLockJournalTable
For more information, see If You're Not Collecting Statistics on Your Dictionary Tables, Do It. Now..