OpenEdge Database - Products Enhancements - Progress Community

 OpenEdge Database

  • Password Policy Management Implementation directly at Openedge Database Level

    • Under Review
    • 1 Comments
    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...
  • Add a "lobmove" qualifier to proutil

    Self-explanatory I think (and overdue...).
  • System table descriptions

    Some of the more recently-added system tables have description values (_file._desc). Please add descriptions for all system tables and views.
  • VSS Backup Support

    • Under Review
    • 0 Comments
    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...
  • 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. ...
  • Stop Adminserver starting on install

    • Under Review
    • 0 Comments
    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...
  • Allow prostrct list when db path is wrong

    • Under Review
    • 0 Comments
    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...
  • Separate Index Selection for WHERE and for BY

    The current implementation of Index Selection Rules practically excludes the BY phrase to be taken into consideration when selecting index(es). At least when developers make sure that it is the WHERE phrase that gets the attention as it limits the number...
  • 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...