Showing results for 
Search instead for 
Did you mean: 
New Member

USE `MicrosoftDataMashup9A8CF2764FB34AECA572E2789EB6B2A2` being sent to Impala via Direct Query



I have connected to Impala with a Direct Query connection.  When I do, I see the following query in the Impala query log on a regular basis during the use of PowerBi (ie its not just a one off when the connection is created but, over an over, multiple times per minute at times).



USE `MicrosoftDataMashup9A8CF2764FB34AECA572E2789EB6B2A2`


This of course fails with a permissions error.  The database doesn't actually exist in Impala.


This is happening with other users as well.


Why is PowerBI trying to connect to this database that doesn't exist?


Why does it not get the message after the first failure?  Smiley Wink


Can we do something (other than create a DB that probably isn't going to be what PowerBI expects anyway) to prevent this happening?  It does make a mess of the query log and is putting a lot of entries into our Denied Access audit logs that we would rather not have to filter away.




New Member

Hi all,

did anyone solve this issue please?



Could you please post the full error message when using DirectQuery mode? And can you successfully connect to Impala database using Import mode?


Community Support Team _ Lydia Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Sorry for the late reply.


The error is only in Impala and it is : 


AuthorizationException: User 'sloongs' does not have privileges to access: MicrosoftDataMashup9A8CF2764FB34AECA572E2789EB6B2A2.*


The problem is that PowerBI is sending a USE statement to use a database called MicrosoftDataMashup9A8CF2764FB34AECA572E2789EB6B2A2 which does not exist in Impala. (the user also doesn't have access to a database of that name, but that is really besides the point).


This isn't a user requested database call.  It is being generated by PowerBI.

I didn't fully answer your question.


We can successfully query the Impala database in both Direct Query and Import modes.


The only issue is that PowerBI is sending the USE `MicrosoftDataMashup9A8CF2764FB34AECA572E2789EB6B2A2`  query to Impala when it shouldn't.


You get the error only in your source, but everything works well in Power BI, right? If so, what is the result when you create the database mentioned in the error message and  give user access to the database?


Community Support Team _ Lydia Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
New Member



I have connected PowerBI to Impala using the built in Impala connectory (Direct Query connection).  Whenever I do this I am seeing an attempt from my user ID to run  USE `MicrosoftDataMashup9A8CF2764FB34AECA572E2789EB6B2A2` in the Impala query logs which then fails as that data base does not exist.


I see other users also generate the same statement.


Any idea what this is trying to do, or why it would be doing it?


If I was to create that database would it be used by anything?



David Hanes

Helpful resources

PBI_User Group Leader_768x460.jpg

Manage your user group events

Check out the News & Announcements to learn more.

Power BI October Update 2021.jpg

Power BI Release

Click here to read more about the October 2021 Release!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Teds Dev Camp Oct. 2021 768x460.jpg

Power BI Dev Camp - October 28th, 2021

Mark your calendars and join us for our next Power BI Dev Camp!

Top Solution Authors
Top Kudoed Authors