Forum Discussion
connect to the same database with 2 different users
- 10 years ago
HI,
I have encounter the same probleme with Web connector (API) in PowerBi.
Unfortunetly you can't connect the same data source with different credentials in the same pbix file i think.
But an alternative solution you can test (or the DBA administrator)
- In the SQL database you can create a few views who combine data of different company
- This view as a particular shema (different of other tables)
- You can attribute specific acces (read only) in this view using the specific shema
And if a day a new company is create you've just modify you're views ;)
Hope it's help you.
If I am understanding this correctly, what you want to do is create a Content Pack in the service and put your data set and report in that content pack. Then, you can share that out with your users and they can load the content pack into their Power BI. Each user could then set the credentials on the data source to their own. You could do the same thing by sending copies of the PBIX file to each user and have them set the credentials on the data source to their own.
Do you have any insight into how this topic plays out with the OPDG? Maybe a workaround that doesn't fall to the data layer where we'd need to change schemas etc. We're in the middle of a POC and at this point the cost of doing that is high.
My company uses multiple user logins for same database to ensure different levels of security. For example we reference the TNSnames.ora file where multiple databases are listed. However there are also multiple logins for a particular database. Some logins use grant selects to get access to lower level schemas, but other are just flat out different and one will never get all access for security purposes. Note: this isn't an issue with our current Business Objects implementation.
I can create 2 separate PBIX files with different logins and locally load the files separately. But if I try to create a another database connection using the gateway with the alternate set of credentials it interprets it as a duplicate connection. Seems to be a deal-killer for schedule refresh, right?
Thanks