问题描述
这篇来自SqlBatman的帖子描述了这种情况与我当前的客户类似，实际上，这表明许多公司依赖大量报告，由于它们对性能的影响，这些报告已转为通宵处理.
This post from SqlBatman describes a situation similar to my current client and, in reality, indicative of many companies that rely on tons of reports which have been shifted to over-night processing because of their performance impact.
我如何开始使用一般的Analysis Services，尤其是OLAP Cubes来帮助我的客户?
How do I get started using Analysis Services in general and OLAP Cubes in particular to help my clients?
推荐答案
我真的很喜欢分析服务逐步赶上SSAS可以做的所有事情.
I really like Analysis Services Step by Step to get up to speed on all that SSAS can do.
简而言之，SSAS使您可以快速访问预聚合的数据.但是，OLAP的真正功能并不是能够快速生成报告.在于能够与数据进行交互.切片，切块，向下钻，向上钻和贯穿.这是一个数据爱好者的梦想.
In short, SSAS gives you quick access to pre-aggregated data. The real power of OLAP is not in being able to generate reports quickly, though; it's in being able to interact with the data. Slicing, dicing, drilling down, up, and through. It's a dataphile's dream.
这就是说，如果您只是想从中获取静态报告，或者想要构建多维数据集，则确实非常非常需要加快数据仓库的速度.为此，请获取数据仓库生命周期工具包的副本. Kimball是这方面的权威，特别是如果您想在其之上使用SSAS.
That being said, if you just want to get static reports out of this, or you want to build out cubes, you really, really, really need to get up to speed on data warehousing. Grab a copy of The Data Warehouse Lifecycle Toolkit for this. Kimball's the authority on this, especially if you'd like to use SSAS on top of it.
仓库是蛋糕，立方体是糖霜.首先，烘烤蛋糕，然后将立方体放到顶部使其变得更好.
The warehouse is the cake, the cube is the icing. Bake the cake, first, and the cube just gets put on top to make it that much better.
干杯，
埃里克
Cheers,
Eric
这篇关于SQL Server Analysis Services和OLAP的开发人员指南的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！