Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
I tried to load some views using DirectQuery mode and I get the error message "Impersonation is not supported in DirectQuery mode. Turn off impersonation or switch to import mode." What does this mean?
Solved! Go to Solution.
@earg73 I was able to fix this error by ensuring that the user that i'm using to connect to the SQL server was specificity mapped as a user on the actual database contained within my view. even if your user is a admin make sure that they are also mapped to the db that your view is accessing.
@earg73 I was able to fix this error by ensuring that the user that i'm using to connect to the SQL server was specificity mapped as a user on the actual database contained within my view. even if your user is a admin make sure that they are also mapped to the db that your view is accessing.
I'm getting the same issue. Let me ask if the circumstances are similar: When importing (get data), I'm logging onto a SQL server database on a local machine or network server. I have to specify credentials for logon (impersonation) because the default for login username uses a concatenation of computername and username (mycomputermyusername)instead of mynetworkname\myusername. I have to do this for SSIS and SSAS as well, but they have no issues with impersonation.
My thought is that import is set up to allow impersonations, but direct query is not. Unless I can set the default for the login username, it looks like the only way to bring in the data is by import.
Any ideas?
I'm thinking that perhaps it has something to do with the EffectiveUsername property setting, which is explained pretty nicely in the knowledge base (LINK).
Have you verified that this setting is working properly?