Timeline for Minimal permissions required to read index size in SQL Server
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 11, 2019 at 14:03 | comment | added | Charles Byrne | db_datareader role does not provide access to filter_definition column on sys.indexes. The has_filter column will show true but the filter_definition is null. So as stated by sepupic some of the metadata won't be visible. | |
| Jul 25, 2017 at 9:00 | comment | added | John K. N. | I agree and read the underlying documentation. Thanks. OP was asking what the minimal requirements would be to access the data. I was just digressing slightly to eventually come back to the least required permissions. | |
| Jul 25, 2017 at 8:47 | comment | added | sepupic | >>>In order to retrieve data for the sys.indexes view you would have to GRANT SELECT ON <object> TO <user> for all the above objects. Sadly, this is not possible, because of the following restrictions...<<< You don't need the SELECT permissions on the above 4 systables but you "see" some data in sys.indexes, exactly the data you have permissions on: "the visibility of metadata is limited to securables that a user either owns or on which the user has been granted some permission", technet.microsoft.com/en-us/library/ms187113(v=sql.110).aspx | |
| Jul 25, 2017 at 8:04 | history | answered | John K. N. | CC BY-SA 3.0 |