问题描述
我确实遇到了以下错误（仅限生产，因为在我的开发环境中我只有几亿行） - 请参阅示例错误以下。
我不知道有实际的限制。它实际上是一个限制 - 或软件中的错误？
DETAILROWS（不是我会找到官方的微软文档）没有记录限制（https://dax.guide / detailrows /）。我没有在所有行上进行DRILLTHROUGH。我事先已将该部分限制为 一两千行，
但错误始终是相同的。如果我手动编写DAX或通过Microsoft Excel运行它也是相同的。
我一直在我的模型中为各种措施实施细节行定义 - 如https://www.sqlbi.com/articles/controlling-drillthrough-using-detail-rows-expressions-in-dax/
来自Analysis Services限制（https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/olap-physical/maximum-capacity-specifications-analysis- services？view = sql-server-2017）我只看到
"表格中的行数" =无限制（警告：限制，表中的任何一列都不能超过1,999,999,997个不同的值。）。 =>我没有那么多不同的值！
那为什么这不起作用？
我发现的唯一其他参考是https：// community .powerbi.com / t5 /桌面/当前查询 - 无法评估 - 因为 - 表 - 包含/ td-p / 312298 - 但这是powerbi和old - 并且没有答案！
任何 提示/建议是受欢迎的。我不希望所有的工作都没有用，如果已经进入钻取经验 - 这是一个很好的有用的功能！
$
当前查询无法针对'*****'表进行评估，因为该表包含超过20亿行。
技术细节：
RootActivityId：1693dad3-8e8c-4f8b-96da-9ab563f52363
日期（UTC）：4/24/2019 12:31:11 PM
0：PFError :: SetLastError（）+ 0x24f
1：PFSetLastError（）+ 0x494
2：0x00007FFBDB035B8A（符号名称不可用）
3：0x00007FFBDA0D906F（符号名称）不可用）
4：XLColumn :: DoAddDataIDOpUnderParent（）+ 0xa0
5：XLColumn :: AddGroupByIntoBuilder（）+ 0x67
6：XLSubcube： ：BuildIMBIQuery（）+ 0x356
7：MDContext :: QueryXLSubcubeAndGetIteratorAndQuerySpec_IMBI（）+ 0x4ba
8：XLPrefetchParticipant :: GetDataIteratorUsingVSBatching（）+ 0x179
9：XLPrefetchParticipant :: GetDataIteratorUsingSEBatching（）+ 0x1fd
10：XLLogOp_SPJ< XLRelLogOp> :: ExecFusionSpoolAdditive（）+ 0x100
11：XLLogOp_SPJ< XLRelLogOp> :: ExecSpool（）+ 0x295
12： XLRelLogOp :: GetIterPhyOpImpl（）+ 0x6a
13：XLRelLogOp :: GetIterPhyOpImpl（）+ 0xb4
14：XLRelLogOp_AddColumns :: MakeIterPhyOp< 0>（）+ 0xac3
15：XLRelLogOp :: GetIterPhyOpImpl（）+ 0x48
16：XLRelLogOp :: GetIterPhyOpImpl（）+ 0xb4
17：XLRelLogOp :: ExecuteRowsetInternal（）+ 0x58
18：XLRelLogOp :: ExecuteRowset（）+ 0x446
19：PCDAXQuery :: ExecuteRowset（）+ 0x1217
20：PCDAXQuery :: ExecuteImpl（）+ 0x20
21：PCDAXQuery :: Execute（）+ 0x161
22：PCASTDMLRootNode :: DispatchExecute（）+ 0x1d21
23 ：PCDMLStatement :: Dispatch（）+ 0x6b6
24：PCXAExecute :: Dispatch（）+ 0x10c4
25：PXSession :: InternalExecuteCommand（）+ 0x9e2
26：PCSession :: ExecuteCommand（）+ 0x9d
27：PCClientRequestHolder :: ExecuteRequest（）+ 0xe7
28：PCRequestHolder :: ExecuteTask（） + 0x17d
29：PFThreadPool :: ExecuteJob（）+ 0x40e
30：PFThreadPool :: WorkerMethod（）+ 0x3a6
31：PFCommandThreadPool： ：ThreadProc（）+ 0x21
32：PFThreadPool :: ThreadProcWrapperForPFThreadPool（）+ 0xb3
33：crt_at_quick_exit（）+ 0x7d
34：BaseThreadInitThunk （）+ 0x22
35：RtlUserThreadStart（）+ 0x34
http://www.hmayer.net/
Hi,
I did run into the following Error (on Production only, because on my dev environment I only had a couple of 100 million rows) - see sample errror below.
I was not aware aware of an actual limitation. Is it actually a limitation - or a bug in the Software?
DETAILROWS (not that I would find an official microsoft documentation) does not have a limit documented(https://dax.guide/detailrows/). I am not doing the DRILLTHROUGH on all the Rows. I have limited the section beforehand to a couple of 1000 rows, but the Error is always the Same.Also the Same if I manually write DAX or run it through Microsoft Excel.
I have been implementing Detail row defintions for various measures in my model - as described by https://www.sqlbi.com/articles/controlling-drillthrough-using-detail-rows-expressions-in-dax/
From the Analysis Services Limits (https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/olap-physical/maximum-capacity-specifications-analysis-services?view=sql-server-2017) I only see
"Rows in a Table" = UNLIMITED (Warning: With the restriction that no single column in the table can have more than 1,999,999,997 distinct values.). => I do not have so many distinct values!
So why is this not working?
The only other reference I found is https://community.powerbi.com/t5/Desktop/Current-query-cannot-be-evaluated-because-the-table-contains/td-p/312298 - but this is powerbi and old - and does not have an answer!
Any Hints / Recommendation is welcome. I do not want all the work to be of no use if have put into the drillthrough experience - and it is a good an usefull feature!
The current query cannot be evaluated for the '*****' table, because the table contains more than two billion rows.
Technical Details:
RootActivityId: 1693dad3-8e8c-4f8b-96da-9ab563f52363
Date (UTC): 4/24/2019 12:31:11 PM
0: PFError::SetLastError()+0x24f
1: PFSetLastError()+0x494
2: 0x00007FFBDB035B8A (symbolic name unavailable)
3: 0x00007FFBDA0D906F (symbolic name unavailable)
4: XLColumn::DoAddDataIDOpUnderParent()+0xa0
5: XLColumn::AddGroupByIntoBuilder()+0x67
6: XLSubcube::BuildIMBIQuery()+0x356
7: MDContext::QueryXLSubcubeAndGetIteratorAndQuerySpec_IMBI()+0x4ba
8: XLPrefetchParticipant::GetDataIteratorUsingVSBatching()+0x179
9: XLPrefetchParticipant::GetDataIteratorUsingSEBatching()+0x1fd
10: XLLogOp_SPJ<XLRelLogOp>::ExecFusionSpoolAdditive()+0x100
11: XLLogOp_SPJ<XLRelLogOp>::ExecSpool()+0x295
12: XLRelLogOp::GetIterPhyOpImpl()+0x6a
13: XLRelLogOp::GetIterPhyOpImpl()+0xb4
14: XLRelLogOp_AddColumns::MakeIterPhyOp<0>()+0xac3
15: XLRelLogOp::GetIterPhyOpImpl()+0x48
16: XLRelLogOp::GetIterPhyOpImpl()+0xb4
17: XLRelLogOp::ExecuteRowsetInternal()+0x58
18: XLRelLogOp::ExecuteRowset()+0x446
19: PCDAXQuery::ExecuteRowset()+0x1217
20: PCDAXQuery::ExecuteImpl()+0x20
21: PCDAXQuery::Execute()+0x161
22: PCASTDMLRootNode::DispatchExecute()+0x1d21
23: PCDMLStatement::Dispatch()+0x6b6
24: PCXAExecute::Dispatch()+0x10c4
25: PXSession::InternalExecuteCommand()+0x9e2
26: PCSession::ExecuteCommand()+0x9d
27: PCClientRequestHolder::ExecuteRequest()+0xe7
28: PCRequestHolder::ExecuteTask()+0x17d
29: PFThreadPool::ExecuteJob()+0x40e
30: PFThreadPool::WorkerMethod()+0x3a6
31: PFCommandThreadPool::ThreadProc()+0x21
32: PFThreadPool::ThreadProcWrapperForPFThreadPool()+0xb3
33: crt_at_quick_exit()+0x7d
34: BaseThreadInitThunk()+0x22
35: RtlUserThreadStart()+0x34
http://www.hmayer.net/
这篇关于详情 - >无法为“...”表评估当前查询，因为该表包含超过20亿行。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！