在 SQL Server 商业智能中，为什么要从 OLAP 多维数据集创建报表模型？
在 Business Intelligence Developer Studio 中，我想知道为什么要从 OLAP 多维数据集创建报表模型。
据我了解，OLAP 多维数据集和报表模型都是面向业务的底层结构（通常是关系数据库）视图，对于业务用户来说可能没有多大意义。多维数据集是维度和度量方面的多维视图，而报表模型是……嗯，我完全不确定——它是一个更面向业务的、但本质上仍然是关系视图吗？
无论如何，在报表生成器中，我可以直接连接到 OLAP 多维数据集或报表模型。所以我不明白为什么，如果我有一个 OLAP 多维数据集，它已经提供了适合最终用户的面向业务的数据视图，为什么我会将其转换为报表模型并在报表生成器中使用它。
我认为我显然错过了报告模型和多维数据集之间的一些根本区别 - 感谢任何帮助！
In Business Intelligence Developer Studio, I'm wondering why one would want to create a report model from an OLAP cube.
As far as I understand it, OLAP cubes and report models are both business-oriented views of underlying structures (usually relational databases) that may not mean much to a business user. The cube is a multidimensional view in terms of dimensions and measures, and the report model is... well I'm not sure entirely -- is it a more business-oriented, but still essentially relational view?
Anyway, in Report Builder I can connect directly to both an OLAP cube or a report model. So I don't see why, if I have an OLAP cube which already provides a business-oriented view of the data suitable for end-users, why I would then convert that to a report model and use that in Report Builder instead.
I think I'm obviously missing some fundamental difference between report models and cubes -- any help appreciated!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
在 SQL Server 2005 中，您仍然必须在多维数据集上创建报表模型才能使用报表生成器。 RB 2.0将直接打开一个立方体，尽管RB不一定支持SSAS的所有可用功能。 此博客Teo Lachev 的条目对此进行了更详细的讨论。
In SQL Server 2005 you still had to create a report model over a cube to use Report Builder. RB 2.0 will directly open a cube, although not all available features of SSAS are necessarily supported by RB. This blog entry by Teo Lachev discusses it in more detail.
一般来说，我同意创建基于立方体的模型没有多大意义。我想您可以使用它来隐藏多维数据集的某些方面，然后您可以使用基于角色的安全性向用户公开不同的模型。不过，我通常不会让 BI 之外的用户在 SSRS 中构建报告，因此这对我来说不是一个令人信服的理由。
如果您没有 OLAP 多维数据集，则报表模型会很好。这是隐藏表连接和字段的复杂性，同时为用户提供获取数据的方法的好方法。这也是为业务用户提供比列在数据库中存储方式更友好的字段名称的机会。
Generally I would agree that there isn't much point to creating a model based on a cube. I suppose you could use it to hide some aspects of the cube and then you could use role based security to expose different models to users. I don't normally let users outside of BI build reports in SSRS, though, so that wouldn't be a compelling reason for me.
Report models are good if you don't have an OLAP cube. It is a good way to hide the complexity of table joins and fields while providing users with a way to get to the data. It also is a chance to provide friendlier names for business users for fields than how the columns are stored in the database.
OLAP 多维数据集的另一个优点是计算引擎。
您可以在多维数据集中包含复杂的计算度量，这些度量在关系数据库中很难创建和/或耗时，但非常适合 Analysis Services。
然后，您可以使用报表生成器向业务用户公开这些计算，隐藏固有的复杂性。
Another advantage of an OLAP cube is the calculation engine.
You can have complex calculated measures in your cube that are hard to make and/or time consuming in a relational database, but are well suited to Analysis Services.
You can then expose those calculations to your business users with Report Builder, hiding the inherent complexity.
安全性和简单性。
您可以针对关系数据库或维度数据库使用报表模型，为用户提供更易于使用的数据视图。
您可能还希望通过仅公开可用列的子集来保护数据库。
您可以更改模型的底层数据源/架构，但保持模型完整，从而确保最终用户的无缝体验。
Security and simplicity.
You can use a report model against a relational or a dimensional database to give a user an easier to use view of the data.
You may also wish to secure your database by only exposing a subset of the columns available.
You could change the underlying data source/schema of the model, but keep the model intact, thus ensuring a seamless experience for end users.