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)
I managed to get rid of this error message by redoing the query steps, one by one. After completing one step then i click on close and apply and save after the applying steps succeed and repeat for second steps.
Anyway, i would like to know the root cause of it so that i can prevent it in future.
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)
it is not true, when i refresh single table which give error on main refresh, error does not appears
Hi Salvador Anonymous Wedson_veras Syed_Abbas-7 Digger
I"m also facing the same error but if while exicuting the my sql query if i limit 100 rows I'm able to load the data
If I'm not limit the rows Im getting this error
while loading the power query I'm able to get if i applay colse&applay in powerbi I'm getting error
How to resove this issue could you please help me on thisHi,
Limiting data size is indeed working for such kind of mentioned issues. However, such limitation is not needed in final production. So we need a tradeoff approach.
Here is a magical approach I am using. I listed the steps below.
1. Define a logic parameter, named as e.g. DebugMode. Set its default value to True.
2. While importing data from data source, limit data size to proper value in case DebugMode = True.
3. Publish your PBI app to specific workspace.
4. Go to the workspace and modify the parameter to False.
5. Update your app.
Please try above approach. Behind it, I suppose PBI server side have stronger performance and capacity to accomodate bigger size of data.
[EDIT]
Hello,I'm not able to use the parameter to condition the request, could you give me a hint please?
Ok I got it : & (if debug then " LIMIT 1000" else "")
