February 15, 2013
- What is the Metaverse?
- How is the Metaverse data stored?
- Is there a limit to how many Metaverse attributes I can have?
- Has access to the metaverse gotten faster with recent releases?
- How do I safely query the metaverse?
- Added (Aug 5 2015): How Many Metaverse Attributes can I have?
Where and how is the Metaverse data stored?
Before I get into that I must caution you that modifying data directly will put you in a position that is unsupported by Microsoft. Even querying the data is something of a touchy issue (see Part 5).
The Metaverse consists of 5 tables in the FIM Synchronization Service Database:
Every object in the metaverse has a row in this table. Single-Valued non-reference attributes are stored in this table
This table has a DateTime column of the same name of every attribute column in the mms_metaverse table (in other words – single-valued non-reference attributes).
This table has a UniqueIdentifier column of the same name of every attribute column in the mms_metaverse table (in other words – single-valued non-reference attributes).
Reference attributes (both single valued and multi-valued) are stored in this table in an Entity Attribute Value format. The references are kept as uniqueIdentifiers
Non-Reference multi-valued attributes are stored in this table in an Entity Attribute Value format (with a column for each of the possible data types)