Object Hierarchy

The ​Object​ hierarchy and fact tables track all key schema (tables, facts, attributes, etc) and application objects (reports, dashboard, cubes, etc) stored in the MicroStrategy Metadata(s) being monitored by Platform Analytics. The object hierarchy does not record data related to configuration objects (subscriptions, schedules, users, user groups, etc). Configuration objects are stored in separate hierarchies.

The ​Object Category​ and ​Object Types​ are groupings/categorizations of different metadata objects. A full List of Object Category and Object Types: is provided at the end of the section.

The ​Component Object​ hierarchy is used to track the relationship between an object and all of its direct child components. An object in the metadata can be both an Object and Component Object in Platform Analytics. The lu_component_object tables are views on the underlying lu_object tables. All objects are stored at the level of Metadata and Project.

The relationship between Objects and their child Component Objects is stored in the fact_object_component table. This table stores only the most recent relationship between an object and its components. For example, if an attribute is removed from a report, it will be removed as a component in the fact_object_component table.

lu_object_category

The ​Object Category​ is a high-level categorization of types of objects in the metadata, such as reports, attributes, documents, metrics, and more. This table and the corresponding attribute act as key filters/selectors for analyzing particular types of objects in the metadata. The data in this table is static and predefined. 

Column	Description	Data-Type
object_category_id	The fixed numeric ID for the Object Category.	smallint(6)
object_category_desc	The fixed list of Object Categories. Sample elements include: Attributes Columns Reports Cubes	varchar(128)

lu_object_type

The ​Object Type​ for a specific ​Object​ stored in the metadata(s) being monitored. This attribute provides more granular grouping options for objects. For example, if an object’s category is Cube, its type may be OLAP Cube or Data Import Cube. The data in this table is static and predefined.

Column	Description	Data-Type
object_type_id	The fixed numeric ID for the Object Type.	smallint(6)
object_type_desc	The fixed list of object Types. Sample elements include: OLAP Cube Data Import Cube	varchar(128)
object_category_id	The numeric ID of the corresponding Object Category. This column is the source of the Object Category attribute.	smallint(6)

lu_object_extended_type

The Object Extended Type for a specific Object Type stored in the metadata(s) being monitored. This attributes provides more granular object types, such as MDX reports or data import cubes. The data in this table is static and predefined.

Column	Description	Data-Type
extended_type_id	The fixed numeric ID for the Extended Type. This column is the source of the Object Extended Type attribute.	int(11)
extended_type_desc	The fixed list of extended Types. Sample elements include: Data Import Google Drive Freeform SQL	varchar(255)

lu_object

The ​Object​ contains the distinct application or schema object stored in the metadata for a specific project. Each object has a unique GUID and is defined at the Project level.

Column	Description	Data-Type
object_id	The auto-generated numeric ID for the object.	bigint(20)
object_guid	The GUID of the Object in the metadata.	varchar(32)
object_name	The name of the Object stored in the metadata. When the object represented by a row is a column (object_type_id = 4, object_category_id = 3), then the DataType of the column is appended to the name as a suffix. For example: ObjectName:SignedInt	varchar(255)
object_desc	The description of the object.	varchar(512)
object_location	The navigation path to the object in the project. For example:  Platform Analytics/Shared Reports/1. Dashboards/Telemetry	varchar(1024)
creation_date	The UTC date when the object was first created. This column is the source of the Object Creation Date attribute.	date
modification_date	The latest date from when the object was last modified. The date will continue to update as the object is modified. This column is the source of the Object Modification Date attribute.	date
creation_timestamp	The UTC timestamp for when the object was first created.	datetime
modification_timestamp	The latest UTC timestamp for when the object was last modified. The timestamp will continue to update as the object is modified.	datetime
object_status_id	The numeric ID of the latest status of the object. The status ID changes based on the latest modification. The status can be: Visible Hidden  Deleted Ad-hoc This column is the source of the Object Status attribute.	tinyint(4)
object_type_id	The numeric ID of the corresponding Object Type. This column is the source of the Object Type attribute.	smallint(6)
project_id	The numeric ID of the corresponding Project.	int(11)
owner_id	The numeric ID of the corresponding Object Owner.	bigint(20)
object_extended_type_id	The numeric ID of the extended type of the object. For example, if the object is a Data Import Cube, its extended type may be Data Import Google Big Query Build a Query. This column is the source of the Object Extended Type attribute.	int(11)
object_version	The version ID of the object.	varchar(32)
object_certified	The flag used to track if the object has been certified in the metadata. The flag can be: Not Applicable N Y	varchar(14)

lu_component_object_category

A view on the lu_object_category warehouse table. This table tracks the categorization of child component objects nested within an Object. The data in this table is static and predefined.

View Table Column	WH Table Column	Description	Data-Type
component_object_category_id	object_category_id	The fixed ID of the Object Component Category.	smallint(6)
component_object_category_desc	object_category_desc	The predefined list of Component Objects.	varchar(128)

lu_component_object_type

A view on the lu_object_type warehouse table. This table tracks the Object Types of child Component Objects nested within an object. It provides a more granular analysis of the Object Category. The data in this table is static and predefined.

View Table Column	WH Table Column	Description	Data-Type
component_object_type_id	object_type_id	The fixed ID for the Component Object Type.	smallint(6)
component_object_type_desc	object_type_desc	The predefined list of Component Object Types. This column is the source of the Component Object Type attribute.	varchar(128)
component_object_category_id	object_category_id	The numeric ID of the corresponding Component Object Category.	smallint(6)

lu_component_object

A view on the lu_object warehouse table. This table lists the distinct application or schema objects stored in the metadata for a specific project. Each Component Object​​ has a unique GUID and is defined at the Project level.

View Table Column	WH Table Column	Description	Data-Type
component_object_id	object_id	The auto-generated numeric ID for the Component Object.	bigint(20)
component_object_guid	object_guid	The metadata GUID of the Component Object.	varchar(32)
component_object_name	object_name	The name of the Component Object stored in the metadata. This column is the source of the Component Object attribute.	varchar(255)
component_object_desc	object_desc	The description of the Component Object.	varchar(512)
component_object_location	object_location	The navigation path to the Component Object in the Project.	varchar(1024)
component_object_type_id	object_type_id	The numeric ID of the corresponding Component Object Type. This column is the source of the Component Object Type attribute.	smallint(6)
component_object_extende d_type_id	extended_type_id	The numeric ID of the corresponding Component Object Extended Type. This column is the source of the Component Object Extended Type attribute.
project_id	project_id	The numeric ID of the corresponding Project.	int(11)
component_object_version	object_version	The version ID of the Component Object.	varchar(32)
component_object_certified	object_certified	The flag used to track if the object has been certified in the metadata. The flag can be: Not Applicable N Y	varchar(14)

fact_object_component

An ​Object​ in MicroStrategy can exist as a standalone entity or it may be used by other objects and therefore can be the ​Component Object​. The relationship between ​Objects​ and their ​Component Objects​ is stored in the fact_object_component table. This table stores only the current direct relationship between an object and its components.  For example, if an attribute is removed from a report, it will be removed from the fact_object_component table. 

Column	Description	Data-Type
object_id	The auto-generated numeric ID for the Object.	bigint(20)
component_object_id	The auto-generated numeric ID for the Component Object.	bigint(20)

List of Object Category and Object Types:

Below is the full list of Object Categories and Object Types tracked in Platform Analytics. 

Object Category	Object Type
Ad Hoc Objects	Ad Hoc Object
Attribute Forms	Attribute Form Category
Attributes	Abstract Attribute
	Attribute
	Attribute Role
	Attribute Transformation
	Derived Attribute
	Recursive Attribute
Cards	Card
Columns	Column
Consolidations	Consolidation
Cubes	Data Import Cube
	OLAP Cube
Custom Groups	Custom Group
	Element Grouping
Derived Elements	Derived Element
Documents	Document
	HTML Document
	Report Writing Document
Dashboards	Dashboard
Element Load Objects	Element Load Objects
Facts	Fact
Filters	Filter
	Filter Partition
	Filter Segment
Folders	User Folder
	System Folder
Hierarchies	System Hierarchy
	User Hierarchy
Managed Objects	Managed Attribute
	Managed Attribute Form
	Managed Column
	Managed Consolidation
	Managed Data Import Cube
	Managed Intelligent Cube
	Managed Database Table
	Managed Derived Element
	Managed Derived Attribute
	Managed Logical Table
	Managed Grid Report
	Managed Hierarchy
	Managed Card
	Managed Folder
	Managed Metric
	Managed Object
Metrics	Data Mining Metric
	Metric
	Metric Extreme
	Metric Subtotal
	Reference Line
	System Subtotal
	Training Metric
Projects	Project
Prompt	Attribute Element Prompt
	Embedded Prompt
	Level Prompt
	Object Prompt
	Prompt
	Prompt Expression Draft
	Value Prompt
Reports	Base Report
	Datamart Report
	Graph Report
	Grid and Graph Report
	Grid Report
	Incremental Refresh Report
	Non Interactive Report
	SQL Report
	Text Report
	Transaction Services Report
Security Filters	Security Filters
Tables	Database Table
	Logical Table
	Partition Database Table
	Partition Logical Table
	Partition Mapping Table
Templates	Template
Transformations	Transformation
Unknown	Unknown

lu_object_status

The latest status of the Object. The ​Object Status​ continues to change as the Object is modified. The status will always reflect the most recent state. An object is defined as an Application or Schema Object stored in the metadata. It does not include the status of the configuration objects (subscriptions, schedules, users, etc). The configuration Objects Status is tracked as a form of the attribute. For example, the Schedule attribute has a status form to track its latest state.

Column	Description	Data-Type
object_status_id	The defined numeric ID for the Object Status.	tinyint(4)
object_status_desc	The current status of the Object. The status changes if the object is modified, i.e. marked as hidden or deleted from the metadata. The object status elements include: Element Load Object Ad Hoc Visible Deleted Hidden	varchar(25)

lu_object_owner

lu_object_owner is a view on the lu_mstr_user table in the warehouse. The lu_object_owner table is used to track the user who created the object or another user who currently owns the object. The owner usually defines the permissions for how the object can be used and by whom.

View Table Column	WH Table Column	Description	Data-Type
object_owner_id	mstr_user_id	The auto-generated numeric ID for the current Owner in the MicroStrategy metadata.	bigint(20)
object_owner_guid	mstr_user_guid	The metadata GUID of the User object.	varchar(32)
object_owner_name	mstr_user_name	The name of the User object in the metadata that has ownership of a particular object.	varchar(255)
object_owner_desc	mstr_user_desc	The description of the User object in the metadata.	varchar(512)
object_owner_login	mstr_user_login	The login of the User object in the metadata.	varchar(255)
creation_timestamp	creation_timestamp	The UTC timestamp of when the user was first created in the metadata. If a script was used to import a list of users, the timestamp may be identical for users. This is expected.	datetime
modification_timestamp	modification_timestamp	The latest UTC timestamp from when the User object was modified. The value will continually update as the User is modified or changed.	datetime
object_owner_status	mstr_user_status	The latest status of the User Object in the metadata. The status can be: Visible Hidden Deleted	varchar(25)
metadata_id	metadata_id	The numeric ID for the corresponding metadata for each User. All users are stored at the metadata level.	int(11)
object_owner_version	object_version	The version ID of the owner of the object.	varchar(32)

fact_object_change_journal

This fact table stores the historical change journal modification information. By joining this table with other lookup tables, like lu_object, lu_account, and lu_account, the user can analyze who changed what object at which time.

The objects that track the change journal information include all the object types in the lu_object_type tables. Adding Change Journal Fact tables to the Platform Analytics Repository enables administrators to analyze the object modification history for all objects in the metadata(s) being monitored by Platform Analytics.

Column	Description	Data-Type
object_id	The auto-generated numeric ID for the fact object. This allows you to determine what project these objects belong to.	bigint(20)
session_id	The auto-generated numeric ID for the fact object. This allows you to determine which Session the change applied to, which client or server the change applied to, and which type of client (i.e. Session Source) the change applied to.	bigint(20)
account_id	The auto-generated numeric ID for the fact object. This allows you to determine who (i.e. account) modified the object.	bigint(20)
change_type_id	The fixed ID for the Object Change Type.	tinyint(4)
transaction_timestamp	MicroStrategy internal use.	datetime(3)
tran_date	MicroStrategy internal use.	date
comments	The comments a user leaves when changes are saved on an object.	longtext

lu_change_type

The Change Type is the object change types a user performs on an object. For example, creating a new object or deleting an object.

Column	Description	Data-Type
change_type_id	The fixed numeric ID of the change type. This is the source column for the change_type_id column of fact_object_change_journal.	smallint(6)
change_type_desc	The fixed list of change types. Change Types include: 0 Reserved 1 Reserverd2 2 Save Objects 3 Reserverd3 4 Delete Objects 5 Garbage Collection 6 Set Change Journal State 7 Get Change Journal State 8 Purge Change Journal 9 Search Change Journal 10 Delete Merge User 11 Find Objects By Paths 12 Copy Object 13 Manipulate source Accounts 14 Notify Cluster Cube Change	varchar(32)