Forum Discussion
Data Capacity
hi hugoberry thank you very much for you reply
can you elaborte more about the checklist? i don't know these things you mentioned.
what is that CommandTimeout? where can I defined it? also don't know what is buffering the data
thanks a lot again
I don't have too much information about your setup so I assumed that in your query you might be using the following Access Data Functions
- Odbc.DataSource might be able to define Connection Timeout in the connection string
- OleDb.DataSource no you Connection Timeout in the connection string
- Sql.Database (most likely) Whcih has the following option: CommandTimeout : A duration which controls how long the server-side query is allowed to run before it is canceled. The default value is ten minutes
Table.Buffer Buffers a table into memory, isolating it from external changes during evaluation.
Table.Combine Returns a table that is the result of merging a list of tables. The tables must all have the same row type structure.
If you don't have too many trade secrets in your M queries to get more precise suggestions.
hugoberry thank you
i added this timeout function and i'm getting this error message again (as above)..
do you know maybe if the problem is on my server? and not on the PBI side?
because it crushed on the 'evaluating' status and not even in the middle of loading the rows
thanks
Depending on your SQL view this could be the case. Can you change the query to be select top 10 * from table to see if it evaluates correctly? What are you getting in SQL Server profiler?
Currently, even without solid document about dataset size limitation for reference, as we tested, big amount of data 90M rows data will have really poor performance in Query Editor. So in this scenario, we suggest you use Direct Query mode.
Regards,
