Hi Bryan,

The SQL Runner has been fully moved to the Web UI Administration Console. We removed it from the Workbench as there was no point keeping it there and maintaining its code since the Web version of the SQL Runner provides better capabilities and improved security.

If you have some reason to use the Workbench SQL Runner rather than the Web UI one, please share them here. 

Hi Etienne, thanks for the confirmation.

Web UI SQL runner is fine. I just thought something is missing in the workbench configuration.

Hi Bryan,

It's true that we've kept the SQL Runner in the workbench for a long time after introducing it in the Web UI, so one might easily take it for granted. But recently we recorded a (minor) security concern on the Workbench SQL Runner, and since it was easier for us to remove it than to address the issue, the decision on what to do was easy to take.

It comes to no suprise that we are working slowly but steadily to get rid of the workbench for "daily" PPM Administration tasks by moving these administration capabilties to the web UI. For example, User Administration & Security Groups management are already available in the Web UI. We won't remove these from the Workbench until we're faced with a similar choice and that removing them from the workbench is the easiest option.

By the way, make sure to click on the "?" small icon at the bottom the Admin Console SQL Runner if you haven't done so yet. You may learn a few things in there, such as the possibility to execute the SQL by pressing CTRL+Enter (like in SQL Developer) or cycling through previously run SQL Queries with CTRL+Up/CTRL+Down.

Fully understood, Etienne. Thanks for your prompt response on this.

Hi Etienne.

I'm back on this topic, after a PPM upgrade.

In the SQL Runner by Admin console there are additional limitations, for example is not possible to check the status of invalid items. This was possible in the SQL Runner by Workbench.

In my understanding, the SQL Runner by Admn console introduces limitation at the query (i.e: custom tables or system table visible at "ppm" schema) but if the "ppm" oracle schema has the grant to view a table/view I don't understand why the Admin console add limitations.

Is there a way (a feature toggle or by any configuration) to remove the limitations managed by the SQL Runner in the Administration Console ?

Hi Silvio,

All the security checks added ot the SQL Runner have been put in place according to mandates from our internal Security Office, and it's not an option to have them turned off by default, or even be able to easily turn them off.

Regarding ways to overcome these security checks, yes we do have some hidden parameters to disable them (in case someone understands the security implications of doing so), but don't expect me to share them too openly.