MicroStrategy Analyst key terms

The logical model of tables, columns, and the joins between them that MicroStrategy uses to turn business questions into SQL against a data source.

A schema object that maps to one physical table or view in a warehouse and exposes selected columns as attributes or facts to the rest of the project.

The warehouse-side table, view, or synonym that a logical table points to, including any namespace prefix and database instance used at execution time.

A business concept used for grouping and filtering, such as Customer or Month, defined by its ID column and optional descriptor columns for display.

One column expression that supplies a value for an attribute, such as the ID form used for joins or a description form used for display.

A single member value of an attribute, like the month January or customer 1042, used when filtering or browsing without forming a full report.

A numeric column that can be aggregated, such as revenue or quantity, stored at the grain of the attributes in its logical table.

The formula, column reference, or join-derived expression that produces a fact's value, which may combine several physical columns or tables.

A declared parent-child link between two attributes, letting the engine infer joins and aggregation levels without a direct table join.

An ordered set of attribute relationships, such as Region to State to City, that supports drilling and level-aware metric evaluation.

A named sequence of attributes and hierarchies that controls which levels a user can drill to or from on a report grid.

A connection definition holding the driver, server, credentials, and connection settings used to run SQL against a particular data source.

The assignment of a logical table to a database instance, and optionally to a namespace, so the engine knows where to execute its SQL.

A report or dataset built from hand-written SQL rather than the schema, useful for sources that are not modeled in the project.

A report type that lets an analyst assemble tables, joins, and filters graphically without writing SQL, then save the result as a dataset.

The process of loading data from files, web services, or other sources into an in-memory cube or warehouse table for analysis.

A precomputed, columnar copy of report results stored on the Intelligence Server that answers matching queries without hitting the warehouse.

A multi-pass, multi-source cube that pre-aggregates data at several levels and applies security filters at query time for fast, governed access.

A scheduled or on-demand rebuild of a cube's contents so cached results reflect current warehouse data.

A server-side store of previously executed SQL results keyed by the exact query, reused when an identical request arrives.

The event where a submitted request is answered from a cube or query cache instead of being sent to the warehouse.

A scheduled pre-execution of common reports or cubes so the first user request of the day is already cached.

A business calculation defined once in the semantic layer, combining a fact expression with aggregation, filtering, and level settings.

A metric built from a single fact or column expression with one aggregation function, such as Sum(Revenue).

A metric whose formula combines other metrics or arithmetic, such as Revenue minus Cost, evaluated from its component definitions.

The set of attributes at which a metric is calculated, controlling grouping and allowing metrics to report at a grain different from the report grid.

The combination of attributes present in a report or metric calculation that determines how data is grouped and aggregated.

A metric whose calculation applies a filter, so only rows meeting the condition contribute to the aggregate value.

A qualification applied inside a metric's definition, evaluated before aggregation, that restricts which records feed the calculation.

A metric whose expression is defined by a formula over other metrics or facts rather than by a stored column.

A metric reviewed and approved by a data steward so it is the trusted, canonical definition that analysts should reuse instead of rebuilding.

The person accountable for a subject area's definitions, quality, and approval decisions, including certifying metrics and resolving definition disputes.

A curated list of business terms with approved definitions and links to the objects that implement them, used to align analysts and consumers.

A rule attached to users or groups that restricts which rows they can see, applied automatically to every query they run.

Access control that limits visible records per user, typically implemented with security filters so different users see different subsets of the same report.

A granular permission, such as Web Reporter or Schema Editor, that determines which product features and objects a user can use.

A named bundle of privileges and object access assigned to users, simplifying administration of who can do what.

The per-object list of users and groups with granted permissions, controlling who can view, modify, or delete a specific object.

The policies controlling what data an AI assistant may read, which prompts and outputs are logged, and which users may invoke it.

Recording natural-language requests and generated responses so administrators can audit AI usage, investigate incidents, and tune guardrails.

The traceable path from a report or metric back through its definitions to source tables and columns, used for impact analysis and audit.