Database server
The hardware specifications for the database server depend on the platform and deployment size.
Processor speed
The following table lists the minimum processor speed that is required for a database server,
depending on the platform and deployment size.
| Platform | Minimum processor speed for small deployments | Minimum processor speed for large and enterprise deployments |
|---|---|---|
| Intel | 2.5 GHz | 3 GHz |
| pSeries | 2.3 GHz | 3 GHz |
Processor quantity
The following table lists the minimum processor quantity that is required for a database server, depending on deployment size.
| Deployment size | Number of processors |
|---|---|
| Small | 2 |
| Large | 4 |
| Enterprise | 4 Add a processor for each additional 10,000 SEs over 10,000, up to a total of 12. |
Memory size
The following table lists the minimum memory that is required for a database server, depending on
deployment size.
| Deployment size | Minimum memory |
|---|---|
| Small |
|
| Large |
|
| Enterprise |
|
TADDM 7.3.0.3, and later: 8 GBDisk space
The following components require
database disk space:
- System catalog
- Tables
- Indexes
- Logs
- Temporary space, for sorts and joins, for example
- Backup space
Disk space and disk drive requirements for a database server are not a function of only disk
capacity. The following table lists some general guidance about disk drive layout on the database
server.
| Deployment size | Number of disk drives (RAID) or disk arms (SAN) required for the TADDM database tables | |
|---|---|---|
| Minimum | Recommended | |
| Small | 2 | 3 or more |
| Large | 6 | 7 or more |
| Enterprise | 8 | 9 or more |
Place database logs on separate disk drives (RAID) or disk arms (SAN) from the TADDM database tables. Database logs are required for large and enterprise deployments.
Initial amount of disk space required for TADDM database
To
estimate the initial amount disk space that is required for your TADDM
database implementation, complete the following steps. These estimates
are based on Level 3 discovery data. Depending on the breadth and
depth of data in your environment, the disk space requirements can
change.
- Use the ci_no variable to represent the number of CIs.
- Use the se_no variable to represent the number of SEs.
- Use the ci_rds variable to represent the amount
of raw disk space for CIs without any additional disk space for growth.
Allow 4000 bytes per CI.
ci_rds = ci_no x 4000
- Use the se_rds variable to represent the amount
of raw disk space for SEs without any additional disk space for growth.
An SE consists of approximately 1000 CIs. Allow 4,000,000 bytes per
SE.
se_rds = se_no x 4,000,000
- Use the tds variable to represent the total
disk space, including some additional disk space for growth. Use one
of the following formulas:
- tds = ci_rds x 1.75
- tds = se_rds x 1.75
This calculation includes additional disk space for temporary space and more.
- Use the chs variable to represent the change
history disk space. The change history disk space is the amount of
space by which the database grows weekly, over and above the initial
disk allocation, depending on the frequency of discovery.
chs = tds x 1.1
This calculation allows for an increase of 10%.
The space requirements increase if additional data is discovered or loaded or if you use the TADDM version management feature.
The following example of a disk space calculation, based
on CIs, is for a large deployment:
- ci_no = 10,000,000
- ci_rds = ci_no x 4,000 = 40,000,000,000
- tds = ci_rds x 1.75 = 70,000,000,000
- chs = tds x 1.1 = 77,000,000,000
- se_no = 10,000
- se_rds = se_no x 4,000,000 = 40,000,000,000
- tds = se_rds x 1.75 = 70,000,000,000
- chs = tds x 1.1 = 77,000,000,000
Prerequisite checker product codes
The following table lists product codes that are used with the prerequisite checking tool.
| Deployment size | Product code |
|---|---|
| Small | TSA |
| Large | TSB |
| Enterprise | TSC |