- Microsoft Tabular Modeling Cookbook
- Paul te Braak
- 407字
- 2021-11-12 16:24:13
Introduction
Prior to the introduction of tabular modeling, which is now commonly known as Business Intelligence Semantic Models (BISM), Microsoft relied on its multidimensional storage model (MOLAP) for Analysis Services (analytical) database. In fact, multidimensional refers to a method of storage, which is still a viable option for enterprise business intelligence through SQL Server Analysis Services (SSAS). The term BISM is not unique to tabular modeling—it also relates to the semantic abstraction of a data model within the MOLAP engine. However, whenever BISM is discussed, it usually relates to tabular modeling (whether that be in PowerPivot or SSAS with a tabular storage mode). The storage engine for tabular modeling is also referred to as xVelocity.
Unlike the xVelocity engine of tabular models, the multidimensional model was basically designed to use a relational source (preferably a SQL Server) as its data source. Additionally, the multidimensional engine assumed that data would be provided through a relational and conformed data structure.
In contrast to this requirement for a single source of data, tabular modeling is designed to support many different data sources which can then be combined in the model as a part of the modeling process. This offers the modeler the ability to combine multiple forms of data within a model, and therefore provides a richer modeling experience. By including additional data sources, model development time can also be greatly reduced, because there is no requirement to source the data from a traditional data mart (or data warehouse).
This chapter examines importing of data from various sources, and managing that data once it has been imported.
Note
The previously discussed statement is not meant to imply that highly optimized models do not require well-structured and conformed databases—they may, when processing times and calculations do not perform satisfactorily. However, one of the benefits of tabular modeling is the ability to apply it at many different levels within an organization. A departmental or subject area solution may be built from an OLTP database, with some information coming from text files, spreadsheets, and other non-traditional (and non-enterprise) sources.
Although there are many data sources available for import (including many different relational database engines), this chapter focuses on some of the more ad hoc ones used by analysts, including text files, reports from reporting services, and data feeds. We also examine how the connection to the database can be managed once it has been created in the tabular model.
- 大話PLC(輕松動(dòng)漫版)
- Learn to Create WordPress Themes by Building 5 Projects
- 零基礎(chǔ)學(xué)Scratch少兒編程:小學(xué)課本中的Scratch創(chuàng)意編程
- Visual Basic程序設(shè)計(jì)教程
- .NET 3.5編程
- Cybersecurity Attacks:Red Team Strategies
- Java面向?qū)ο蟪绦蛟O(shè)計(jì)
- Clojure for Machine Learning
- Microsoft 365 Certified Fundamentals MS-900 Exam Guide
- 編寫(xiě)高質(zhì)量代碼:改善Objective-C程序的61個(gè)建議
- Django 3.0入門與實(shí)踐
- Xamarin Blueprints
- Puppet:Mastering Infrastructure Automation
- Microsoft HoloLens By Example
- 程序員的算法趣題2