This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

What We're Working On for DPA (Updated January, 2021)

To receive updates on the DPA roadmap, JOIN thwack and BOOKMARK this page

Here is a partial list of the things we are currently working on. Your comments and feedback are always welcome and have been vital in shaping Database Performance Analyzer into the product it is today. We are always listening, so please forward your feature requests, problems and use-case stories.

  • Update monitored DB registration wizards to not require privileged user credentials
    • Enable registration wizards to accept an existing DB login for use as the monitoring user instead of creating a new monitoring user. This enables registration wizards to execute with reduced roles (e.g., no sys, sysadmin, or sa privileged role requirements) similar to what is supported with the mass registration option today.
  •  Enhanced Security Capabilities and Configurations
    • Integrate with CyberArk to store/manage authentication credentials
    • Leverage SignPath as well as additional web application security enhancements
  • Support Google Cloud SQL managed databases
  • Alert status enhancements:
    • Improved workflows, filtering, and sorting
    • Alert status for instances on home page
    • Webhook notifications
  • Add area baselines to new Resources metric charts

See and vote on all features here: Database Performance Analyzer Feature Requests

Please note that the above indicates what we are currently working on but is not a guarantee that these features will be delivered should difficulties, circumstances, or priorities change. 

Releases

Parents
  • How is cdb/pdb/multi-tenant support coming along?  We are working on setting up a patching schedule, and it seems like the best way to meet our goals is to go pluggable....  WIth a container db that has one pluggable at a particular version, say 12.1.0.2 PSU1, and an empty container that has 12.1.0.2 PSU2....  We unplug from the PSU1 container and plug into the PSU2 container (all on the same server), ta-daa!  The database is patched.  Unfortunately, DPA needs to be able to connect to pluggables in order to make this feasible.  SO, we are loking for insight as to when support in DPA will be available.

Reply
  • How is cdb/pdb/multi-tenant support coming along?  We are working on setting up a patching schedule, and it seems like the best way to meet our goals is to go pluggable....  WIth a container db that has one pluggable at a particular version, say 12.1.0.2 PSU1, and an empty container that has 12.1.0.2 PSU2....  We unplug from the PSU1 container and plug into the PSU2 container (all on the same server), ta-daa!  The database is patched.  Unfortunately, DPA needs to be able to connect to pluggables in order to make this feasible.  SO, we are loking for insight as to when support in DPA will be available.

Children
No Data