Friday, February 15, 2013

Secrets of the Metaverse Part 2

Parts 1-5:

    1. What is the Metaverse?
    2. How is the Metaverse data stored?
    3. Is there a limit to how many Metaverse attributes I can have?
    4. Has access to the metaverse gotten faster with recent releases?
    5. How do I safely query the metaverse?

    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:

    Table Comment
    mms_metaverse Every object in the metaverse has a row in this table. Single-Valued non-reference attributes are stored in this table
    mms_metaverse_lineagedate 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).
    mms_metaverse_lineageguid 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).

    mms_mv_link

    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
    mms_metaverse_multivalue 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)

    No comments: