Timeline for Can't create indexed view against table with masked columns
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 1, 2018 at 11:01 | history | tweeted | twitter.com/StackDBAs/status/959018743396478976 | ||
| Jan 29, 2018 at 13:14 | history | edited | Aaron Bertrand | CC BY-SA 3.0 |
deleted 54 characters in body; edited tags; edited title
|
| Jan 29, 2018 at 13:08 | answer | added | Aaron Bertrand | timeline score: 3 | |
| Jan 29, 2018 at 12:56 | vote | accept | Dmitri Trofimov | ||
| Jan 29, 2018 at 12:44 | comment | added | Jeroen Mostert | Speculation: this interferes with view expansion, where the optimizer might decide to use an indexed view rather than the table for better performance. With masked columns, it would also be required to check that this optimization is safe, for every query, based on the user's permissions, or "copy" the mask restrictions from the base table to the view before the other logic, or disable view expansion altogether. Rather than pay the cost for any of these, the engineers opted to ensure these features never interact by forbidding any combination of indexed views with dynamic security and masking. | |
| Jan 29, 2018 at 11:14 | answer | added | Stijn Wynants | timeline score: 6 | |
| Jan 29, 2018 at 8:58 | review | First posts | |||
| Jan 29, 2018 at 9:11 | |||||
| Jan 29, 2018 at 8:54 | history | asked | Dmitri Trofimov | CC BY-SA 3.0 |