Sizing Guidelines
You can optionally use the following information to set up your repository. The numbers below assume a maximum of 10,000 schedules will be created at this site. In addition, review the logic below to be sure it applies to your environment.
ReportCaster Guidelines for Sizing the Relational Tablespaces
|
Table Name |
Rows |
Max Rows Width (bytes) |
Notes |
|---|---|---|---|
|
BOTACCES (Report Library only) |
2,000 |
292 |
One record per access list and 1:m with BOTLIST. |
|
BOTADDR |
2,000 |
101 |
One record per address list and 1:m with BOTDEST. |
|
BOTCAT (Report Library only) |
20,000 |
751 |
One record for each schedule in the library. If the schedule is burst, each burst report is a record. |
|
BOTCDATE |
20,000 |
807 |
Could have multiple records per record in the BOTSCIT file (an average number might be 20). Added for the custom scheduling interval feature. |
|
BOTDEST |
20,000 |
210 |
One record per destination. |
|
BOTDIST |
|
|
|
|
BOTJOURN |
|
|
|
|
BOTLDATA (Report Library only) |
10,000 |
NA |
One record per report in the library (blob). |
|
BOTLIB (Report Library only) |
10,000 |
713 |
One record per report in the library (blob). |
|
BOTLIST (Report Library only) |
20,000 |
298 |
One record per destination. |
|
BOTLOG |
10,000 |
228 |
One record per job run and a 1:m with BOTLOG2. |
|
BOTLOG2 |
100,000 |
361 |
One record per job message. |
|
BOTPACK |
10,000 |
124 |
One record per schedule. |
|
BOTPARMS |
5,000 |
369 |
One record per parameter per task. |
|
BOTSBDS |
500 |
625 |
One record per designated blackout day per group. |
|
BOTSCHED |
10,000 |
2252 |
One record per schedule. |
|
BOTSCIT |
10,000 |
590 |
Could have one record per record in the BOTSCHED file. Added for the custom scheduling interval feature. |
|
BOTSIT |
|
|
|
|
BOTSTATE |
1 |
256 |
Contains one record. Added for the Failover feature. |
|
BOTTASK |
15,000 |
928 |
One task per schedule (can have multiple tasks per schedule so 1:m relationship with BOTSCHED). |
|
BOTTELL |
|
|
|
|
BOTTSKEX |
15,000 |
324 |
One per task. |
|
BOTWATCH |
20,000 |
330 |
One record per record in the BOTCAT file. Added for the Library Watch List feature. |
The following formula for allocating table space sizes is recommended:
Storage needed = number of bytes of user data x overhead factor
For simple tables (one per table space), an overhead factor of 1.75 is recommended.
Note: The BOTLDATA table uses the BLOB data type, so you should size accordingly.