v6r2013x db深度潜水学习目标在本模块结束时您应该能够.pdfVIP

BASICS FOR THE V6 DATABASE Some Definitions – 1/2 Table – Primary data structure in the database consisting of rows and columns ENOVIA V6 uses three kinds of tables: MX tables for General Administration data and some global vau ata LX for vau ata (see below), IX tables for indexed attributes Index – Data structure in the database for accelerating access to data via indexing columns on commonly accessed tables ENOVIA V6 creates database indexes during the installation procedure The term “Index” in MQL refers to special tables for attributes of V6 – they are not indexes from a database point of view (the IX tables mentioned above) Correct tuning of indexes is essential to maintaining acceptable application performance Note: starting at V6R2011x, there is a new “validate indexes” command to check the OOTB indexes those actually defined in the database Views – Virtual tables meant to keep critical information in memory for fas ccess There are two default views starting in V6R2013 – they require that the Oracle schema owner have the “create view” priviledge Vault – ENOVIA-specific organization of data. By default there are 3 ernance vaults (eService Production, eService Admin and eService Sample) and 1 VPLM vault (vplm) By default, eService Production vault is used for all CBP applications VPM exclusively (for the moment) uses vplm vault Vaults are identified internally with 8-digit hex OIDs stored in the MXLATTICE table Note on OIDs per Vault The OID generation algorithm is based on a signed, 32-bit integer. It can generate an OID in the range -2^31 ~ 2^31-1 (4B+ values). However, for practical purposes we need to leave “gaps” between the OID values for fast generati