IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Data Warehouse solutions
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Plan considerations for the Tivoli Data Warehouse
In a large or enterprise environment, you have the option of using multiple databases for the Tivoli Data Warehouse or having all of your hub monitoring servers use one single database. The benefit of using one database across your environment is that the information is stored in one location, meaning that you can more and accurately generate reports that reflect your entire environment (as opposed to needing to collate reports from several different databases).
However, because the amount of data that is generated during history collection across a large or enterprise environment can be immense, carefully plan the scale and performance of that database.
In addition to the planning information below, the IBM redbook Tivoli Management Services Warehouse and Reporting, SG24-7290, provides database performance tuning information. You can download the book at the following location: http://www.redbooks.ibm.com/abstracts/sg247290.html?Open.
- Estimate the required size of your database
One of the factors to consider when planning the size of database that you need is the amount and type of information you will collect for agent history data collection. Each of the agent user's guides provide capacity planning information to help you calculate the amount of disk space required by data for each attribute group.
- Understanding the disk requirements for your database
Consider the factors in this section when designing a disk subsystem to support your database processing.
- Increase the size of your database (DB2 for Linux, UNIX, and Windows only)
DB2 for Linux, UNIX, and Windows Workgroup Edition has a default table size limit of 64 GB with a page size of 4 KB. To increase the capacity of your DB2 for Linux, UNIX, and Windows database, you can create a new table space, IBMDEFAULTGROUP, and choose a larger page size (up to 32 KB). This increases the capacity of the database up to 512 GB per table.
Parent topic:
Tivoli Data Warehouse solutions