Tableau plans to release a new feature called Virtual Connections. This will allow for individual tables to be extracted and made available in Tableau Server without the need to tie them together via joins or Relationships. Row-level security policies can be applied there as well, with the results persisting to downstream content (not sure about Prep flows, though).
While the initial version won't support incremental data refreshes, there's still a lot of promise here for the admin insights data sources. If all the base tables can be extracted and kept reasonably up to date, all the data sources can be built against the virtual connection, with all the speed one might hope for, and with the only database impact being that of extract refreshes.
One issue with using these right out of the gate is that there is no way to import or export a virtual data connection. So in terms of implementing Admin Insights on top of them, we'd have to have individual admins set the vconn up themselves, then perhaps have them edit the data sources we provide here to point to their local version. Not sure if that'll work, honestly, but worth looking into.
Tableau plans to release a new feature called Virtual Connections. This will allow for individual tables to be extracted and made available in Tableau Server without the need to tie them together via joins or Relationships. Row-level security policies can be applied there as well, with the results persisting to downstream content (not sure about Prep flows, though).
While the initial version won't support incremental data refreshes, there's still a lot of promise here for the admin insights data sources. If all the base tables can be extracted and kept reasonably up to date, all the data sources can be built against the virtual connection, with all the speed one might hope for, and with the only database impact being that of extract refreshes.
One issue with using these right out of the gate is that there is no way to import or export a virtual data connection. So in terms of implementing Admin Insights on top of them, we'd have to have individual admins set the vconn up themselves, then perhaps have them edit the data sources we provide here to point to their local version. Not sure if that'll work, honestly, but worth looking into.