OpenEdge Database - Products Enhancements - Progress Community

 OpenEdge Database

  • VSS Backup Support

    • Under Review
    We would like to see VSS backup support for the openedge database. Customers who use tools like VMWare or other third party backup solutions use VSS integration on SQL , Exchange, and Oracle to do automated backups. This can be accomplished by using...
  • Password Policy Management Implementation directly at Openedge Database Level

    • Under Review
    In the context of different security audit point, the auditors are always pointing the following shortcoming : "when accessing directly the Openedge database, a password is required to authenticate the user but no password policy applies (for example...
  • Stop Adminserver starting on install

    • Under Review
    Ref the problems encountered in KB: 19590. Can we have an option to not start the Adminserver when installed OE. Thanks Chris.
  • Real database triggers and stored procedures (ABL)

    Currently database triggers are run on the client side. The SQL side of the database has stored procedures (java) which can’t be called from ABL directly. Implement ABL database triggers and ABL stored procedures that are run in the database engine...
  • Automatically enable large files

    Enabling large files should be a standard behavior when creating a new database with f.e. prostrct create. Now you have to do this in a separate step, which is often forgotten.
  • Allow prostrct list when db path is wrong

    • Under Review
    If you copy the DB to different path and you have no valid .st file there is no way to repair the db. The list command should always work and just export the .st files with the current paths (or maybe just with dots). The user can then correct them manually...
  • Start the web server for OpenEdge Management/Explorer earlier when the AdminServer...

    In the 'old' days when we still had the Progress Explorer Tool on Windows, you could start the PET and connect to the AdminService almost immediately after the service was started. This allowed you to very quickly see which resources are configured...
  • Add a "lobmove" qualifier to proutil

    Self-explanatory I think (and overdue...).
  • prostrct create possibility to use kilobyte value for -blocksize

    Currently when creating a new database one has to type prostrct create database .. -blocksize X , where X is the desired block size in bytes. Should one happen to make a typo, say 8191 instead of 8192, one might get a database with 4kb block size. ...
  • Virtualisation best practices

    I'm missing documentation, whitepapers and best practices around virtualisation. Like it or not but big parts of large systems are running in virtual environments and VMWare, OpenStack, NetApp, 3PAR, SAN-solutions etc is very common in everything...