Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Azure Data and AI Architect Handbook

You're reading from   Azure Data and AI Architect Handbook Adopt a structured approach to designing data and AI solutions at scale on Microsoft Azure

Arrow left icon
Product type Paperback
Published in Jul 2023
Publisher Packt
ISBN-13 9781803234861
Length 284 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Olivier Mertens Olivier Mertens
Author Profile Icon Olivier Mertens
Olivier Mertens
Breght Van Baelen Breght Van Baelen
Author Profile Icon Breght Van Baelen
Breght Van Baelen
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1: Introduction to Azure Data Architect
2. Chapter 1: Introduction to Data Architectures FREE CHAPTER 3. Chapter 2: Preparing for Cloud Adoption 4. Part 2: Data Engineering on Azure
5. Chapter 3: Ingesting Data into the Cloud 6. Chapter 4: Transforming Data on Azure 7. Chapter 5: Storing Data for Consumption 8. Part 3: Data Warehousing and Analytics
9. Chapter 6: Data Warehousing 10. Chapter 7: The Semantic Layer 11. Chapter 8: Visualizing Data Using Power BI 12. Chapter 9: Advanced Analytics Using AI 13. Part 4: Data Security, Governance, and Compliance
14. Chapter 10: Enterprise-Level Data Governance and Compliance 15. Chapter 11: Introduction to Data Security 16. Index 17. Other Books You May Enjoy

Modes in tabular models

By default, tabular models use an Import mode to load data into memory. An ETL tool such as Power Query extracts the data from data sources, transforms it, and loads it into memory. Afterward, DAX queries can be performed against the in-memory database to calculate and aggregate the data. When tabular models query data residing in memory, processing can be very fast, but the data also needs to be refreshed with the ETL tool every now and then to reflect the most recent changes.

DirectQuery mode is very different from Import mode. Queries are run against the underlying data sources instead of the in-memory database. This means the data is always up-to-date and no refreshes of the in-memory database need to be scheduled, but latencies are higher, meaning performance is worse. Another benefit of DirectQuery mode is that the data model can grow beyond the memory size limits as no copy of the data is kept in memory.

When performing a DAX query against a tabular...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime