19 votes2 comments · Power BI Ideas » Gateways (Enterprise and Personal) · Flag idea as inappropriate… · Admin →Darryll Petrancuri commented
It is up to the SQL Server application architects / developers of the database used as the data source for a DirectQuery to implement the Security Policy and Security Function that will cause proper predicate and block filtering to be enforced by the SQL Server Query Engine.
It is the responsibility of the Enterprise Gateway to set the SESSION_CONTEXT after connecting to the SQL Server database (and determining the database server version since SESSION_CONTEXT only applies to SQL Server 2016).
I understand this means that each user of the Power BI Service who uses a Power BI Model that is dependent on DirectQuery would need their a separate connection to SQL Server 2016 established through the Enterprise Gateway. The connection would still be made using the user established by the Enterprise Gateway administrator but SESSION_CONTEXT would be different for each user signed into the Power BI Service in this case.
This fact should not serve as a blocker to fixing this critical defect in the implementation of the gatewayDarryll Petrancuri shared this idea ·