[Progress Communities] [Progress OpenEdge ABL] Forum Post: Extent management on replication enabled database

Status
Not open for further replies.
T

Tarmo R

Guest
What is the best practice of managing database extents for a replication enabled database running on 10.2B08? If i create the extents structure the way I like it and add a variable extent to the end of each area, then how should I go about adding new extents? I understand, that the normal practice of removing the variable extent before adding new properly sized fixed extents is not possible on replication enabled databases without breaking and re-enabling replication from scratch. Should I just accept, that there will be a 64kb extent in between big extents and the next one will again be a properly sized data extent? This would also be solved by having an ability to define an initial size for a variable extent instead of the maximum, but there seems to be no way for that?

Continue reading...
 
Status
Not open for further replies.
Top