Forum Discussion
OLE DB or ODBC error: [DataSource.Error] MySQL: Fatal error encountered during data read.
Hello Anonymous,
I'd say there was an error on one of the steps, perhaps it wasnt shown on the query editor, (you'd need to refresh in every single step), and there's also the possibility that some data that wasnt being loaded in the query editor was causing the error (i.e, a # when a numeric value is expected, i've suffered a couple of times by replacing # by empty spaces after setting the data type to numeric, even tough it might work in the query editor, when the full data set is loaded it will give an error)
Hi,
Here is my update after more guess and validation. I would like to share my opinion on this topic.
After applying query change or refreshing reports, we can observe loading progress of each table. There is one table showing quite many rows loading and spending a lot of minutes. However the table actually contains very limited number of records. Thinking of calculation with SelectRows(), I narrowed down both couping tables to several records and then observed the kind of couping leading to multiplication of both table row numbers during loading. So far, root cause was basically identified.
Then, after moving mentioned calculation to data preparition phase because the calculation is unrelated to all data slicing, the loading is very very fast, just actual size of row both table loaded as per prompt. Of course, offloading dynamic calculation to report with DAX should also be another option.
After all, it can be concluded that couping b/w tables put multiplying load in loading. As a result, often dataset often fails due to expiry.
Hope helpful for you!
Can I talk to you in private, I have the same problem and I suffered a lot with that problem