Oracle® Retail POS Suite 14.1/Merchandising 14.1.1 Implementation Guide Release 14.1.1 E63051-02 |
|
![]() Previous |
![]() Next |
This chapter lists the approximate hard drive sizes that are required at each store to be able to support the Data Import project.
The following assumptions were made to arrive at an approximate capacity:
The archival period is one week.
The frequency is one import bundle per day.
Tax, Customer and Currency imports where not included in the bundles.
Peak Load for the EMPLOYEE Import is 30 employees per file.
The Peak Load Capacity of each file is taken into consideration for the estimation. See Table 4-1, "File Sizes".
The average compression ratio in creating a jar file is considered to be 60%.
As the frequency is one bundle per day, and the archival period is one week, therefore the maximum number of files on the disk is eight.
A footprint on the DDI (Data Distribution Interface) on the Store Server is considered to be the size of one bundle and added to the final estimate. The footprint on the DDI is not part of the scope of the DIMP.
Because the peak load size for Merchandise Hierarchy is not defined, a load of 5000 records is estimated.
Table 4-1 identifies the file sizes for components in the data import at a store.
Table 4-1 File Sizes
Type of Import | One-Record Size in Bytes | Peak Load (Number of Records) | Peak File Size in Bytes |
---|---|---|---|
Item |
950.00 |
15,000,000.00 |
14,250,000,000.00 |
Pricing |
1,600.00 |
820,000.00 |
1,312,000,000.00 |
Store |
710.00 |
5,000.00 |
3,550,000.00 |
Merchandise |
300.00 |
5,000.00 |
1,500,000.00 |
Employee |
1,400.00 |
30.00 |
42,000.00 |
15,567,092,000.00 Bytes
Table 4-2 identifies the sizes of data import bundles.
Table 4-2 Bundle Size
Bundle Size (jar Size) |
Assuming 60% Compression Ratio in creating a jar |
9,340,255,200.00 |
Bytes |
Approximate Bundle Size |
8,900.00 |
MB |
|
8.69 |
GB |
Table 4-3 identifies the required hard-drive capacities to enable a data import.
Table 4-3 Hard Drive Capacity
Seven files in Archive + One File in current |
71,200.00 |
MB |
|
69.53 |
GB |
||
Approximate Hard Drive Size to retain the Bundles |
70.00 |
GB |
|
Footprint on DDI Store Server (the DDI remains the responsibility of the implementation team to implement) - assuming size of one Bundle |
78.69 |
GB |
80.00 GB
Table 4-4 Item Import Data Volumes
Data Volumes | ||
---|---|---|
Item |
800,000 – 1.5 million for peak season |
1.5 million |
5000 – 15,000 for delta |
||
Item Location |
See Item |
See Item |
Item (Merchandise) Hierarchy |
number of departments |
number of departments |
groups |
number of groups |
|
number of hierarchies |
number of hierarchies |
|
Organizational (Store) Hierarchy |
5000 stores, 6 levels |
5000 stores, 6 levels |
number of regions |
||
number of districts per region |
||
number of stores per district. |
||
Tax data |
See Item (since any tax information is limited to item-related attributes such as tax group ID). *Tax information does not come from Oracle Retail Merchandising System . |
See Item (since any tax information is limited to item-related attributes such as tax group ID). *Tax information does not come from Oracle Retail Merchandising System. |
Data Volumes: 800000 price changes per day per store.