Main steps for OpenEdge table partitioning
- Last Updated: January 17, 2024
- 2 minute read
- OpenEdge
- Version 13.0
- Documentation
In today’s 24x7 business environment, Progress OpenEdge mission-critical databases are necessarily growing larger and larger. The task of running and managing very large tables in very large databases can be very challenging. OpenEdge table partitioning is also known as horizontal table partitioning because it breaks up a table by row into smaller, more manageable chunks called partitions. You can then run and manage each partition individually. OpenEdge implements table partitioning at the database level, not at the application level. Logically, partitioned tables still appears as one single unit to the application. Physically, it is stored in multiple partitions in the database. A business application that accesses non-partitioned tables can also access partitioned tables with little or no changes required.

OpenEdge table partitioning is integrated throughout the OpenEdge environment, including in OpenEdge Management, OpenEdge ABL, and command line tools.
Main steps for implementing table partitioning
- Identify tables to partition
Identify the new and existing tables that you want to partition and their associated partition columns and local and global indexes.
- Allocate space for the tables being partitioned
Create a structure description (.st) file to allocate space for the tables being partitioned.
- Enable table partitioning for a database
Enable table partitioning for the database using the Database Administration Console.
- Create new partitioned tables
Create new partitioned tables using the Database Administration Console or the OpenEdge ABL API.
- Partition existing tables
Partition existing tables using the Database Administration Console or the OpenEdge ABL API.