5.12.5 Criteria for determining the Item management database size
This section describes the criteria for determining the Item management database size (S, M, L, or LL). This size is specified for the -s option of the jsssetup.bat command (setup command) or the jssdbinit.bat command (Item management database initialization command).
- S: Suitable for a small-scale test environment or for an intra-company query management system
-
Number of Items registered per day: 3 to 5
Assumed number of users: 5 to 10
Maximum number of Items that can be registered: About 7,700#1
Maximum number of attached files that can be registered: About 3,000 #2
Size of area for storing Items and attached files: 3 GB #3
- M: Suitable for a medium-scale operation management system
-
Number of Items registered per day: 5 to 30
Assumed number of users: 10 to 50
Maximum number of Items that can be registered: About 45,000 #1
Maximum number of attached files that can be registered: About 17,000 #2
Size of area for storing Items and attached files: 20 GB #3
- L: Suitable for a large-scale operation management system
-
Number of Items registered per day: 30 or more
Assumed number of users: 50 or more
Maximum number of Items that can be registered: About 121,000 #1
Maximum number of attached files that can be registered: About 35,000 #2
Size of area for storing Items and attached files: 50 GB #3
- LL: Suitable for a large-scale operation management system (consisting of 20 or more subsystems)
-
Number of Items registered per day: 30 or more
Assumed number of users: 50 or more
Maximum number of Items that can be registered: About 200,000 #1
Maximum number of attached files that can be registered: About 110,000 #2
Size of area for storing Items and attached files: 90 GB #3
- #1:
-
Calculation of this value assumes that one Item is about 54 KB.
- #2:
-
Calculation of this value assumes that one attached file is about 256 KB. If larger files are attached, the maximum number of attached files that can be registered decreases.
- #3:
-
Unavailable area might arise in the storage area if data is not saved efficiently.