Analysis Services 分区问题
我有一个度量组，每天进行分区。我可以处理特定分区，并且 XMLA 命令成功完成。此外，我确保每个度量组至少处理一个分区，因此我的多维数据集是“部分处理的”，我应该能够浏览它。
问题...在此度量组内的任何度量的多维数据集中都看不到数据。真正让我发疯的是，我可以捕获 SSAS 对服务器执行的 SQL 命令，并且它返回行！ 但果然，当我检查刚刚处理的分区的属性时，它说它的大小是 0.0 MB。它也没有切片，不知道是否有帮助。
如果有人见过这样的事情并且有任何想法......我洗耳恭听。
I have a Measure Group, that is partitioned daily. I can process a particular partition, and the XMLA command completes successfully. Furthermore, I have ensure at least one partition is processed for every Measure Group, therefore my cube is "partially processed" and I should be able to browse it.
The problem... no data can be seen in the cube for any of the Measures within this Measure Group. What is really driving me crazy is that I can capture the SQL command that SSAS is executing against the server, and it returns rows!
Yet sure enough, when I check the properties of the partition I just processed, it says it's size is 0.0 MB. It also has no slice, don't know if that helps.
If anyone has seen anything like this and has any idea... I am all ears.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您必须设置分区片。这就是 SSAS 如何确定数据应驻留在该分区中。如果没有切片器，它将丢弃读取的行。查看 http://sqlcat.com/technicalnotes/例如 archive/2007/09/11/ssas-partition-slicing.aspx。
You must set a partition slice. That is how SSAS determines that the data should reside in that partition. Without the slicer it is discarding the rows read. Check out http://sqlcat.com/technicalnotes/archive/2007/09/11/ssas-partition-slicing.aspx for example.
您眼前的问题不太可能是由于缺少切片而导致的。正如 Mosha 所解释的 这里，出于性能原因，定义分区的切片细节非常重要。这是他的一句话：
上面说，如果没有定义分区片，那么SSAS将无法通过仅从相关分区扫描来优化某些查询。
但它也说，没有定义切片，它仍然应该返回正确的结果，尽管可能慢得多。作为旁注，它还暗示如果切片定义不正确，那么可能会返回错误的结果，或者根本不返回任何结果。
由于您的分区没有定义切片，因此问题一定出在用于创建分区的 SQL 查询绑定上。 您是否检查过 SSAS 中的数据源配置是否正确？当您手动运行查询时，您可能已连接到与为 SSAS 多维数据集配置的 SQL Server 实例不同的 SQL Server 实例（例如 UAT 与产品）。
Your immediate problem is unlikely to be because of the missing slices. As Mosha explains it here, defining slicing details for partitions is very important for performance reasons. Here is a quote from him:
The above says that if partition slices are not defined, then SSAS will not be able to optimize certain queries by scanning only from the relevant partitions.
But it also says that with no slices defined it should still return the correct results, albeit probably much slower. As a side-note, it is also implied that if slices ARE defined BUT improperly, then it could happen that wrong results get returned, or nothing at all.
Since your partitions have no slices defined, rather the problem somehow must be with the SQL query bindings used for creating the partitions. Have you checked that the data source is configured correctly in SSAS? When you were running the query manually you might have been connected to a different SQL server instance than the one configured for the SSAS cube (e.g. UAT vs. PROD).