Posted: 6 Dec 2015 23:08 EST Last activity: 6 Apr 2018 19:26 EDT
Custom Tables - 32K table space necessity
We are doing upgrade from 5.5 to 7.1.9 (DB-UDB). Existing application is having rules and Data tables in 7K table space. Since v7 required 32K table space, in ever step of upgradr (like Migration, Rules Upgrade, Data Upgrade), we are generating ddl's (using generateddl.sh or migrate.sh scripts) and applying them to DB manually. Before applying we are editing all create table scripts to create in 32K table space, for both Rules tables and Rules Data tables.
Now question is about existing application Custom tables, they are created earlier (day1 when this application was built) in 16K table space. Now do we really need to move those tables to 32K table space ? If we dont do what is the impact and if we want to move them to 32k, is there any steps/scripts provided/suggested by Pega team to handle such scenarios ?
Please help with what ever info help us to make move. Thanks.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
A tablespace is a logical storage unit which is used by the database internally to store data. Each tablespace consists of one or more datafiles which physically hold the data in relevant data structures. From this understanding, as long as your allocated space for custom tables - 16k holds the data you have in those tables with no space issues and have room to grow when required, you should be not worrying about that setting as this is more of a DB space thing than anything to do with Pega processing.