Microsoft Azure Documentation

Understanding Models in Azure Analysis Services

Azure Analysis Services (AAS) provides a cloud-based platform for enterprise-grade data modeling. Models are the core of AAS, serving as the semantic layer that business users interact with. This documentation explores the concept of models within AAS, their components, and best practices for their creation and management.

What is an Analysis Services Model?

An Analysis Services model is a collection of tables, relationships, calculations, and metadata that represents business data in a structured and understandable way. It's designed to simplify complex data from various sources, making it accessible for reporting and analysis tools like Power BI, Excel, and Tableau.

Key Components of an AAS Model:

Types of Models

Azure Analysis Services primarily supports tabular models. These models store data in memory and use a column-store database engine for high performance. They are developed using tools like Visual Studio with Analysis Services projects or SQL Server Data Tools (SSDT).

Developing and Deploying Models

The process of creating and deploying an AAS model typically involves the following steps:

  1. Connecting to Data Sources: Establish connections to your chosen data sources (e.g., Azure SQL Database, Azure Data Lake Storage, SQL Server).
  2. Importing Data: Select the tables and columns you need and import them into your model.
  3. Defining Relationships: Create relationships between tables based on common keys.
  4. Creating Measures and Calculations: Write DAX expressions for your business logic.
  5. Designing Hierarchies and Perspectives: Organize data for intuitive user interaction.
  6. Deploying to Azure Analysis Services: Publish your model to an AAS instance in the Azure portal.
  7. Refreshing Data: Schedule or manually trigger data refreshes to keep the model up-to-date.

Tip: Dimensional Modeling

For optimal performance and user experience, it is highly recommended to design your AAS models using dimensional modeling principles (Star Schema or Snowflake Schema). This involves separating data into fact tables (containing transactional data and measures) and dimension tables (containing descriptive attributes).

Best Practices

Important Note on Model Compatibility Levels

When creating or upgrading models, pay attention to the compatibility level. Higher compatibility levels unlock newer features but may require specific versions of client tools and may not be compatible with older Analysis Services versions. Always choose the highest compatibility level supported by your Azure Analysis Services engine version.

Related Topics