How can MS be touting Power BI as an enterprise BI delivery platform but not support this feature is beyond me.Īnd, to take it a step further, I frankly don't understand how Azure SQL Data Warehouse does not yet support row level security when you consider that it is designed to be an MPP relational data warehouse that should eliminated if not dramatically reduce the need for Analysis Services. The fact this is properly implemented for SQL Server Analysis Services and not for SQL Server 2016 or Azure SQL Database is absurd and patently unacceptable. To me, this is a glaring case of the Power BI team not understanding the capabilities of SQL Server 2016 and the teams not speaking to each other. This means that the enterprise gateway must establish a separate connection (which hopefully it already does) for each 'end user' signed into Power BI. What needs to happen is that the enterprise gateway must determine the database platform is has connected to (after establishing the connection), and if it determines the platform is SQL Server 2016 or Azure SQL Database it needs to set the SESSION_CONTEXT, providing the value of the key 'UserID' from the encrypted credentials that were passed from Power BI (desktop or service) to the connection. Row level security in both environments can rely on the actual user connection to the database or to information provided via SESSION_CONTEXT. There is an unacceptable and glaring defect in the implementation of the Enterprise Gateway to SQL Server 2016 / Azure SQL Database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |