Update Schema

Pre-requisites: Login as the schema owner of the MM_SYSTEM_* tables (usually SDE). If on a multiple database instance such as MSSQL, ensure you connect to the same database where the MM_SYSTEM_* tables reside (usually SDE). After login, run the Upgrade ArcFM Solution Database and Create/Update ArcFM Solution Tables tools.
IMPORTANT: Microsoft SQL users: Login to the database that holds the core MM_ tables (not the GIS or PX databases, for example). Failure to login to the correct database will result in tables being created with broken relationships.

You will not be able to access any other tabs in the CU Administration tool until the Update Schema tool has been executed. This tool creates and updates the tables and relationships required for the tools in CU Administration to function properly (for a complete list, see the section at the end of this topic). Follow the steps below to update your geodatabase to use the CU Administration tools.

  1. In ArcCatalog, ensure you are logged into the geodatabase as the owner of the system tables.
  2. Click the CU Administration tool. If you do not see this tool in ArcCatalog, it may need to be added to a toolbar. See the Find the CU Administration Tool section on the CU Administration page.
  3. Click the Execute button to launch the Update Schema tool. It is not possible to select just one item and run the tool on only that item.
  4. When the Update Schema tool is finished, it will show the action it took and the table's or relationship's status to the right of its name.

What Does the Update Schema Tool Create?

The Update Schema tool creates the following tables, relationships and model names.









  • CUAttributeRelationship

  • CUExtendedDataRelationship

Field Model Names

The following field model names are added to the Designer Field Model Name domain.

IMPORTANT: CU_LIBRARY_IDAssigned to the ID field on the MM_CU_LIBRARY table. This field provides a unique ID for CUs.Deleting system tables results in some possibly unforeseen side effects. If you delete the MM_CU_LIBRARY table, then all filter relationship classes will be deleted as well. If you must delete MM_CU_LIBRARY, then delete the rest of the MM_CU_* system tables as well (those listed above).


The MM_CU_SEARCH_XML table will need to be set with read and write permissions. All other tables will need to be read only for the editor role. For users responsible for creating filters, you will also want to apply read and write permissions to the MM_CU_DOMAINFILTER table for them.

QR code for this page

Was this helpful?