Datamart与Reporting Cube的区别是什么? [英] Datamart vs. reporting Cube, what are the differences?

问题描述

这些术语到处都是，我不知道清晰的定义.我很确定我知道什么是数据集市.而且我已经使用Business Objects和Cognos之类的工具创建了报表多维数据集.

The terms are used all over the place, and I don't know of crisp definitions. I'm pretty sure I know what a data mart is. And I've created reporting cubes with tools like Business Objects and Cognos.

我还让人们告诉我，数据集市不只是多维数据集的集合.

I've also had folks tell me that a datamart is more than just a collection of cubes.

我也有人告诉我，数据集市是一个报表多维数据集，仅此而已.

I've also had people tell me that a datamart is a reporting cube, nothing more.

您了解什么区别?

推荐答案

多维数据集可以(并且可以说应该是非常特定的意思-通过 OLAP服务器(例如 MS Analysis Services 或Oracle(nee Hyperion) Essbase .但是，它的使用也更加宽松.这种OLAP多维数据集使用感知多维数据集的查询工具，这些查询工具使用与标准关系数据库不同的API.尽管OLAP服务器可以实现，但通常会维护自己的优化数据结构(称为 MOLAP ).作为关系数据源(称为 ROLAP 的前端)或多种混合模式(称为 HOLAP )

Cube can (and arguably should) mean something quite specific - OLAP artifacts presented through an OLAP server such as MS Analysis Services or Oracle (nee Hyperion) Essbase. However, it also gets used much more loosely. OLAP cubes of this sort use cube-aware query tools which use a different API to a standard relational database. Typically OLAP servers maintain their own optimised data structures (known as MOLAP), although they can be implemented as a front-end to a relational data source (known as ROLAP) or in various hybrid modes (known as HOLAP)

我会尽量具体化，并专门使用多维数据集"来指代OLAP服务器(例如SSAS)上的多维数据集.

I try to be specific and use 'cube' specifically to refer to cubes on OLAP servers such as SSAS.

业务对象的工作原理是通过一个或多个来源(可以是关系数据库，OLAP多维数据集或平面文件)，并创建称为

Business Objects works by querying data through one or more sources (which could be relational databases, OLAP cubes, or flat files) and creating an in-memory data structure called a MicroCube which it uses to support interactive slice-and-dice activities. Analysis Services and MSQuery can make a cube (.cub) file which can be opened by the AS client software or Excel and sliced-and-diced in a similar manner. IIRC Recent versions of Business Objects can also open .cub files.

令人讨厌的是，我认为Business Objects位于真正的OLAP系统(例如ProClarity)和即席报告工具(例如 Brio .往返查询面板使它作为纯思想流OLAP工具有些笨拙，但确实提供了传统报表无法提供的一定程度的交互性.我认为Business Objects的优势体现在两个地方:不一定熟悉SQL的工作人员的临时报告，以及提供以交互式格式提供的计划报表，以允许对数据进行一定程度的深入研究.

To be pedantic I think Business Objects sits in a 'semi-structured reporting' space somewhere between a true OLAP system such as ProClarity and ad-hoc reporting tool such as Report Builder, Oracle Discoverer or Brio. Round trips to the Query Panel make it somewhat clunky as a pure stream-of-thought OLAP tool but it does offer a level of interactivity that traditional reports don't. I see the sweet spot of Business Objects as sitting in two places: ad-hoc reporting by staff not necessarily familiar with SQL and provding a scheduled report delivered in an interactive format that allows some drill-down into the data.

数据集市" 也是一个相当宽松的术语，可以表示任何用户-面向数据仓库系统的数据访问介质.该定义可能包括也可能不包括报告工具和元数据层，报告层表或其他项目(例如多维数据集或其他分析系统).

'Data Mart' is also a fairly loosely used term and can mean any user-facing data access medium for a data warehouse system. The definition may or may not include the reporting tools and metadata layers, reporting layer tables or other items such as Cubes or other analytic systems.

我倾向于将数据集市视为进行报告的数据库，尤其是当它是整个数据仓库体系结构中易于定义的子系统时.但是，将其视为面向用户的报告层是相当合理的，尤其是在存在临时报告工具(例如Business Objects或OLAP系统)的情况下，该工具允许最终用户直接获取数据.

I tend to think of a data mart as the database from which the reporting is done, particularly if it is a readily definable subsystem of the overall data warehouse architecture. However it is quite reasonable to think of it as the user facing reporting layer, particularly if there are ad-hoc reporting tools such as Business Objects or OLAP systems that allow end-users to get at the data directly.

这篇关于Datamart与Reporting Cube的区别是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！