BI 仪表板向下钻取的最佳方式

发布于 2024-11-05 08:00:55 字数 119 浏览 0 评论 0原文

对于 BI 仪表板图表的每次钻取,MDX 查询的最佳方式是什么?例如,如果每次向下钻取有四个钻取级别,我们应该在初始时间执行四个 MDX 查询或仅执行一个查询,并将四个钻取级别的所有数据保留在对象集合中。如果可以请举例说明。

What is the best way of MDX querying for each drill down of BI dash board chart? as a example if you have four drill level every drill down we should execute four MDX query or execute only one query in the initial time, and keep all data of four drill levels in object collection. If you can please explain with a example.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

随风而去 2024-11-12 08:00:55

这在很大程度上取决于您使用什么工具来显示 BI 仪表板。是 SSRS、PerformancePoint 还是其他?

  1. 提取初始 MDX 查询中的所有数据,配置仪表板软件以显示顶级详细信息,并为用户提供向下钻取选项。当用户向下钻取时,取消隐藏下一层详细信息。此选项仅需要到数据库 1 次往返。因此,最初加载仪表板可能会慢一些,但向下钻取体验会非常快(因为数据已经检索到)。

  2. 仅提取初始 MDX 查询中的顶级详细信息,配置仪表板软件以显示结果并为用户提供向下钻取选项。当用户向下钻取时,仪表板软件将发送另一个 MDX 查询,以从数据源检索下一级详细信息。此选项将需要多次往返数据库...一次用于用户首次加载仪表板时的初始顶级详细信息,另一个用于用户每次向下钻取时。

任一选项都可以,但您需要在权衡利弊后决定哪个选项最适合您的需求...

  • 仪表板和数据源之间的网络速度有多快?
  • 您的数据源可以处理多少并发量?
  • 提取所有内容的查询有多大?
  • 速度对您的用户有多重要?

如果您不确定,请确定并测试每个。

This depends a lot on what tool you are using to display the BI Dashboard. Is it SSRS, PerformancePoint, something else?

  1. Pull all the data in the initial MDX query, configure the Dashboard software to display the top level of detail and provide user with options for drilldown. As users drilldown, unhide the next level of detail. This option only requires 1 roundtrip to the database. So intially loading the dashboard may be a bit slower, but drilldown experience will be very fast (since the data has already be retrieved).

  2. Pull just the top level of detail in the initial MDX query, configure the Dashboard software to display results and provide users with options for drilldown. As users drilldown, Dashboard software will send another MDX query to retrieve the next level of detail from your data source. This option will require multiple roundtrips to the database...one for the intial top-level of detail when the user first loads the dashboard, and another for each time the user drills down.

Either option will work but you'll need to make the call on which option best suits your needs after weighing the pros and cons...

  • how fast is the network between your dashboard and the datasource?
  • how much concurrency can your data-source handle?
  • how "big" is the query to pull everything?
  • how important is speed to your users?

be sure and test each if you are unsure.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文