So for years and years, I’ve been able to run my SQL clients (originally Navigator then TOAD for Oracle and some other TOAD variant (not “For Data Analysts”)) and I had been able to do two critical things through many different client versions:
EXEC a basic remote procedure - it doesn’t really matter what it does bottom line is I can’t EXEC something
DEFINE a parametric variable value inline in the code. Typically I’d do this at the start of the code like:
and then subsequent references to that variable like "where MonthDate=’&&ChosenDate’ would use that defined variable. If I chose a setting called “SCAN DEFINES” I wouldn’t need to be prompted when running the script.
^ The beauty of this is I can change values right in the script, run it and then save the script as a bona fide record of what was run for that month. When you are prompted for inputs, you don’t retain the values and should something go amiss you have no record of what was actually run unless you build up a logging table but that’s overkill for the more-ad-hoc analytics and reporting environment I’m in.
Seems like TDP has no support for either of these?? I suspect there may be some things that can get me close but not exactly but there’s also the daunting task of migrating a huge amount of code that had gone for years painlessly through many versions of Quest / TOAD products.