MicroStrategy and Informatica Enterprise Data Tools

The Aggregator transformation in Informatica allows aggregation expressions to contain aggregate functions (SUM, COUNT, etc.), conditional clauses (CASE/DECODE), nested aggregate functions (AVG(SUM(x))), and even non-aggregate functions for conditional logic. This flexibility enables complex aggregation logic within a single transformation, supporting sophisticated data summarization requirements.

Stored Procedure Transformation in Informatica is Passive (does not change the number of rows), Unconnected (can be called from other transformations using :SP syntax), and Connected (can be used directly in the data flow). It is NOT Active because it cannot increase or decrease row count. The combination A, C, D correctly describes all applicable characteristics.

Joiner Transformation is specifically designed to join data from heterogeneous sources residing in different locations or file systems. Source Qualifier reads source data, Lookup looks up values from a flat file or relational table, and Stored Procedure executes database procedures - none are designed for joining heterogeneous sources across locations.

When a Sequence Generator transformation reaches its end value and is configured to cycle, it simply loops back to the start value and continues generating numbers rather than failing the session.

CEIL always rounds UP to the nearest integer, so CEIL(125.12) = 126. CEIL returns the smallest integer greater than or equal to the input value - it never rounds down.

In Aggregator transformation, group by ports (the keys) are stored in the index cache for efficient grouping operations, while the result set (aggregated values) is stored in the data cache. This separation optimizes both memory usage and processing speed.

Connected lookup is flexible and can use either static cache (loaded once at session start) or dynamic cache (updated during session) depending on configuration. The cache type is determined by the lookup cache properties.

When any parameter in DATE_DIFF is NULL, the function returns NULL. This is standard NULL handling behavior - NULL propagates through calculations in Informatica (and SQL), making the entire result NULL.

The statement is false because while Command and Email tasks are indeed non-reusable, Session tasks CAN be reusable. A reusable session can be created once and used in multiple workflows, sharing the same configuration - this is a key workflow design feature.

When Update Strategy transformation is used in mapping, the session property 'Treat rows as' defaults to 'Data Driven' - allowing the transformation to control row-by-row treatment via DD_UPDATE, DD_INSERT, and DD_DELETE flags.

Data Warehousing is the comprehensive process that includes both reporting and analysis as core functions. Data Mining is a technique within analytics, Data Mart is a subset of a data warehouse, and Data Scraping is about data collection, not analysis.

By default, metrics are calculated at the lowest attribute level (most granular data) to ensure accuracy. Calculating at higher levels first can lose precision due to aggregation. The lowest level provides the most detailed foundation for metric calculations.

Report creation is typically restricted to Report Designers who have the technical expertise to build reports, and Administrators who have the permissions. Report Analysts generally consume and analyze existing reports rather than create them.

The default join type for metrics is typically an outer join to ensure that metric values are calculated even when some dimensions have null values. Inner joins would exclude records with null dimension values, potentially losing data.

Filter definitions can be created based on either attributes (dimensional data) or metrics (calculated values). Both options are available when defining filter prompts in BI tools, giving flexibility in how users can filter their data views.

The Total Sales % metric combines existing metrics (TS TY and TS LY) through mathematical operations, making it derived. Since it involves multiple base metrics calculated together, it is also a compound metric. Therefore, it belongs to both categories.

In MicroStrategy, the tilde (~) symbol in a metric definition explicitly specifies that the calculation should be performed at the report level rather than at the attribute level. This controls the aggregation scope of the metric.

With standard filtering and grouping, the Sales metric calculates at the Category level (parent attribute) and includes only the SubCategory records that are actually displayed in the report after filtering is applied. It excludes filtered-out subcategories from the aggregation.

MicroStrategy Web architecture is fundamentally three-tier or four-tier, not two-tier. It requires a web server, application server, and database server at minimum, making it inherently multi-tier in design and deployment.