Your plan is require different queries for the same data set! this is what you are saying if you are granting select on columns. I can no longer have one query/report where one user runds the query and can see the column level data, and the other user runs the exact same query but the column returns nulls. By making the query fail for users without select rights makes this option unusable, way too much governance/cost. You force the creation and management of views which has less overhead than managing two queries ie two reports for the same purpose. Just make the engine return nulls for columns people don't have access to, don't fail the query, or come up with another approach becuase this one is no bueno. Thanks!
No CommentsBe the first to comment
Recent ideas
OneLake Catalog full-text and content search
Why is it not possible to search OneLake by item description or even content? So I was thinking about how a user can find a table if they don't know in which lakehouse it is located? Why can't you se...TePe17 hours agoHelper IVPlanned1.1KViews21likes5Comments