While not a perfect solution, I tried this as a test: Add a SQL filter to the analysis by clicking on any column in the criteria, add filter, convert to SQL and then change the SQL to say "1 = 0" It adds the 1=0 to the WHERE clause and in the test I ran, a query that took about 4 minutes to run initially, came back…

Having the default for all prompts to limit by None would be consistent with OBIEE dashboard prompts. I also wonder about the performance of populating limited prompts that come from multiple dimensions in a star schema. Would have to join through fact, right?

Makes transition between Classic and DV seamless.

Default could be "No log" with options for "Summary Log" and "Detail Log".

Agree

January 2020 release for Autonomous Database includes built-in SMTP.. why not do the same for OAC? "Autonomous Database now includes the UTL_SMTP package. This makes it possible to send emails via PL/SQL from within Autonomous Database. However, note that the only supported email provider is Oracle Cloud Infrastructure…

My concern would be how do you limit the dataset to a reasonable size that Explain would work on a Subject Area? We have tables with several hundred million fact rows and dimensions with hundreds of thousands of rows. We would not want users to kick off an explain plan on that. Best approach is to run a data flow with…

Or at a minimum pre-populate an SR with all relevant instance details