Table Space Size Considerations
Although the easiest way to allocate space is to make one big table space to hold all objects, performance issues frequently dictate that you reduce disk contention by spreading objects out to table spaces on multiple disks. A couple of standard practices include the following:
-
While separating the indexes from the tables on which they are based is simple to do, separating high-use and/or concurrently used tables and indexes from each other is more of an ongoing process and varies greatly from site to site. Keep in contact with your application consultants to determine which tables and indexes are used most heavily at your site.
-
The initial sizing of table spaces must be treated as a starting point, not a final solution. Your application consultants should work with Lawson consultants to determine initial space requirements. There is a spreadsheet they can fill out to estimate sizes. Expect to make many adjustments as you move into production and beyond.