Sizing Guidelines > Reference: Estimation of Initial Database Size > Estimation of Initial BI Data Warehouse Size
  
Estimation of Initial BI Data Warehouse Size
The estimation of the initial data warehouse size involves a determination of the size of key ERP tables, and a subsequent calculation, which depends on the modularization, to convert these sizes into an estimated data warehouse size. Follow the calculation and description to estimate the initial data warehouse size.
Note: There is no guarantee that this estimate gives an accurate size for the initial data warehouse size, it is provided as an approximate method of generating an order-of-magnitude estimate on the initial data warehouse size.
Note: SQL-Server uses a large amount of extra disk space for temporary manipulation of transformational data and you must make allowance for this. The estimate below only considers an approximation for the BI database, excluding requirements for SQL-Server temporary files.
Determine the size of all the following tables in the source QAD ERP database and use these in combination with the “Size Factor” to calculate an estimate of the initial data warehouse size.
 
Initial Data Warehouse Sizing (Page 1 of 2)
Module
Table
Source
Size Factor**
Source ERP Table Size
(Size Factor) * (Source Size)
Financials
ap_mstr
SE
1
 
 
ar_mstr
SE
2/3*
 
 
ard_det
SE
1
 
 
ck_mstr
SE
1
 
 
ckd_det
SE
1
 
 
gltr_hist
SE
1
 
 
tr_hist
SE + EE
1/10*
 
 
ee_CInvoice
EE
1
 
 
ee_CInvoiceMovement
EE
1
 
 
ee_DInvoice
EE
1
 
 
ee_DInvoiceMovement
EE
1
 
 
ee_Posting
EE
1
 
 
ee_PostingHist
EE
1
 
 
ee_PostingLine
EE
1
 
 
Order Management
so_mstr
SE + EE
1
 
 
sod_det
SE + EE
1
 
 
idh_hist
SE + EE
1
 
 
ih_hist
SE + EE
1
 
 
ar_mstr
SE + EE
1/3*
 
 
tr_hist
SE+EE
1/10*
 
 
Operations (assuming all sub modules - Purchasing, Inventory, OEE)
wo_mstr
SE+EE
1
 
 
wod_det
SE+EE
1
 
 
tr_hist
SE+EE
4/5*
 
 
op_hist
SE+EE
1
 
 
po_mstr
SE + EE
1
 
 
pod_det
SE + EE
1
 
 
prh_hist
SE + EE
1
 
 
 
 
 
 
 
 
Enterprise Asset Management (EAM)
work_order
 
1
 
 
equip_down
 
1
 
 
lab_deta
 
1
 
 
squaks
 
1
 
 
 
 
 
 
 
 
Transportation Management (TM) - assuming SQL Server source
xmshdr0
 
1/10*** x
1/3**
 
 
xmsitm0
 
1/10*** x
1/3**
 
 
xmsovr0
 
1/10*** x
1/3**
 
 
xmsxpk0
 
1/10*** x
1/3**
 
 
xmsypk0
 
1/10*** x
1/3**
 
 
xmtpasp0
 
1/10*** x
1/3**
 
 
xmtpesp0
 
1/10*** x
1/3**
 
 
xmtpfsp0
 
1/10*** x
1/3**
 
 
xmtpssp0
 
1/10*** x
1/3**
 
 
Total Source Size for Conversion
X
Estimated Initial BI DW Size
X*(100)
Estimated Size of Initial BI Database = (X)*100
Allow for this amount of space at a minimum. Further, if this total comes to under 500 GB it is recommended that you set up at least a 500-GB disk allowance.
* TABLE NOTE 1: A “size factor” of less than one indicates that not all transactions in the specified table are used by the relevant BI module and you should take this into account in size estimations. For example, in the BI Financials Module, the ar_mstr table has a size factor of 2/3, indicating that only two-thirds of all transactions on the ar_mstr table are converted into aggregated BI data in the BI Data Warehouse.
** TABLE NOTE 2: The source tables might contain data for many years (n years, say n=10 years). For example, if the data warehouse is going to be populated with only three years worth of data (y=3), then you should apply an additional size factor of y/n (in this case 3/10) to the relevant source ERP tables. And you should include this extra size factor in the table above and in the calculations to determine the estimated initial size of the data warehouse.
*** TABLE NOTE 3: TMS source can be a SQL Server database. Assuming that is the case, apply this factor. It is different for different types of source databases.