Examples

If Oracle is the database manager, use the calculations from Oracle; if SQL Server is the database manager, use the SQL Server calculation.

1. The following example illustrates how to calculate the database storage space required for a report that contains logical items, such as statements. The example plans for indexing one million items per month and keeping the index data in the database for 24 months. The table lists information about the database fields.

   Table 1. Database storage for a report that contains logical items

   Field Name	Field Type	Field Size	Index or Filter
   Report Date	Date	4 bytes	Index
   Account Number	Fixed String	12 bytes	Index
   Invoice Balance	Decimal	8 bytes	Filter
   Customer Name	Variable String	20+4 bytes	Filter

        TableSize = ( 4 + 12 + 8 + ( 20 + 4 ) ) = 48
   
        IndexSize = 19 + ( 4 + 8 ) + ( 12 + 8 ) ) = 51
   
        DatabaseSize = ( ( 48 + 40 ) * 1.5 ) + ( 51 * 2 ) ) = 234
                         * 1,000,000 = 234000000
                           * 24  =  5616000000

   Content Manager OnDemand requires 5.6 GB of magnetic disk space to store 24 months of report index data in the database.

2. The following example illustrates how to calculate the database storage space required for a report that contains line data with a sorted transaction value. Because only one database row is generated for each indexed group of pages in the report, in general, significantly less database storage space is required than for reports that contain logical items.

   Reports that contain line data with a sorted transaction value use a fixed type of indexing, where each database row contains the beginning value, the ending value, and the beginning page number for the group of pages. Content Manager OnDemand maintains the beginning and ending values as indexes and the page number as a filter. The main parameters for the calculation are the length, in bytes, of the sorted transaction value, the number of pages generated in a month, the size of a group of indexed pages, and the number of months that Content Manager OnDemand maintains the index data in the database.

   The example plans for indexing one million pages per month, in groups of 100 pages, and keeping the index in the database for 24 months. The table lists information about the database fields.

   Table 2. Database storage for a report that contains a sorted transaction value

   Field Name	Field Type	Field Size	Index or Filter
   Report Date	Date	4 bytes	Index
   Begin Transaction Value	Fixed String	10 bytes	Index
   End Transaction Value	Fixed String	10 bytes	Index
   Page Number	Integer	4 bytes	Filter

        TableSize = ( 4 + 10 + 10 + 4 )  = 28
   
        IndexSize = ( 19 + ( 4 + 8 ) + ( 10 + 8 ) + ( 10 + 8 ) ) = 67
   
        DatabaseSize = ( ( 28 + 40 ) * 1.5 ) + ( 67 * 2 ) ) = 236
                         * ( 1,000,000/100 ) = 2360000
                            * 24  =  56640000

   Content Manager OnDemand requires 56.6 MB of magnetic disk to store 24 months of report index data in the database.