What causes Native database query execution failed?

The native SQL query references a table, view, or stored procedure that was renamed or dropped. The database user running the query lacks permission to execute the specific SQL statement. The SQL syntax is valid in Power BI Desktop but not in the target database version. A stored procedure parameter value is invalid or out of expected range. A query against a view that references a broken underlying table

How do I fix Native database query execution failed?

Copy the native query from Power BI Desktop (Transform Data → Advanced Editor) and run it directly in SSMS or your database client.. Confirm all referenced tables, views, and stored procedures still exist and have not been renamed.. Verify the service account running the refresh has EXECUTE permission on stored procedures and SELECT on all referenced objects.. If a view is involved, check that the view itself is not broken due to underlying schema changes.. Test the query with the same credentials and database context that the gateway uses (impersonation level).

High severityquery

Power BI Refresh Error:
Native database query execution failed

What does this error mean?

The native SQL query (passed directly to the data source) returned an error. This error surfaces when a dataset uses native database queries instead of the standard Power Query connector.

Common causes

1The native SQL query references a table, view, or stored procedure that was renamed or dropped
2The database user running the query lacks permission to execute the specific SQL statement
3The SQL syntax is valid in Power BI Desktop but not in the target database version
4A stored procedure parameter value is invalid or out of expected range
5A query against a view that references a broken underlying table

How to fix it

1Copy the native query from Power BI Desktop (Transform Data → Advanced Editor) and run it directly in SSMS or your database client.
2Confirm all referenced tables, views, and stored procedures still exist and have not been renamed.
3Verify the service account running the refresh has EXECUTE permission on stored procedures and SELECT on all referenced objects.
4If a view is involved, check that the view itself is not broken due to underlying schema changes.
5Test the query with the same credentials and database context that the gateway uses (impersonation level).

Frequently asked questions

Does this error only affect the dataset or also the report?

The error occurs during the refresh — if the refresh fails, the report shows the last successfully loaded data, not an error. Users won't see a broken report, but the data will be stale.

How do I find which Power Query step is causing the error?

Open Power BI Desktop and attempt a refresh. Power Query highlights the failing step in the Query Editor. The error message typically includes the table name and step name.

Can query errors be caused by data changes in the source?

Yes — if the source returns a data type the query doesn't expect (e.g., a null value in a previously non-nullable column), the query evaluation fails.

Does this error affect all tables in the dataset?

Usually only the table whose query evaluation failed. Other queries in the dataset may succeed unless they depend on the failed query's output.

Source · learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-tshoot