OpenEdge Database - Products Enhancements - Progress Community

 OpenEdge Database

  • Dataserver: Provide the ability to access tables that have ‘unsupported datatypes...

    Progress – Product Suggestion Product: Dataserver Enhancement Provide the ability to access tables that have ‘unsupported datatypes’ by simply excluding those fields from the meta-schema, and this allowing the other fields to be...
  • Support environment variables for Database Server in Progress Explorer

    Progress explorer does not support environment variables for Database Server. Progress explorer supports environment variables for AppServers, WebSpeed, NameServers. Example use case: Need database server to run in a time zone different than the...
  • Make default srvrAppMode Production instead of Development

    Having srvrAppMode set as Development in ubroker.properties allows access to the workshop website via cgi-scripts. The workshop allow access to basically everything (Database and Operating System) with admin privileges and no authentication of any kind...
  • TDE Key Management System of Keystore File and KMIP Integration

    Enhancement Request Requirements Encryption keys (Database Master Key *.ks file), the passphrase for the User account and the passphrase for Admin account must be stored within a FIPS 140-2 Level 3 compliant keystore away from the encrypted data....
  • Need datatype for efficient usage of GUID unique ID

    Hi, currently we are using a CHARACTER - GUID ("eb149dfe-c01f-50ac-3a14-66c56c902384") in many tables for unique ID. Analyses of database storage shows that this is highly inefficient on storage and most likely on performance as well. ...
  • Allow 0 column size string parameters in the ODBC driver

    Currently, the ODBC throws an error if an application calls SQLBindParameter for a string parameter and specifies a column size of 0. This is common behavior for ODBC wrapper libraries, particularly in dynamic languages; there is a workaround option for...
  • Ability to query database and object sizes using VSTs or other similar mechanism

    • Under Review
    • 0 Comments
    We want to be able to query database size and individual object sizes. The prefered mechanism would be VSTs but something similar would be OK. It should be queryable remotely by ABL and SQL. This feature has a lot of applications, but right now our...
  • Renumber system indexes

    Currently there is a fairly orderly numbering of tables in OpenEdge databases: >32767: SQL views >0: application tables -1 to -79: metaschema/SQL-89 views/physical structure -80 to -125: SQL catalog -200 to ?: audit/auth/logging -300 to -361?...
  • Delete the database even if the index rebuild has failed

    When you do an index rebuild and it fails or it is aborted, you cannot delete the database with PRODEL. The folowing error will apear: "Index reconstruction utility was aborted. Rerun it to completion. (651)"
  • Remove extent on a target replica database

    It is not possible to remove an extent on a target replica database. Any Storage Area/Extent type cannot be removed on the target database when replication is enabled, as the before-image file needs to first be truncated before removing extents which...