For example, when database sizing for a superstore that sells office supplies, you will need to account, in your calculations, for an abnormally high number of transactions at the end of August, just before school year starts. Furthermore, there may be seasonal trends to consider. For example, a sales application that sells grocery products is likely to need more disk space than one that sells furniture, because a single grocery transaction contains more items than a furniture transaction. Of course, when estimating the number of business transactions that may need to be stored in a given period, and the disk space required to accommodate this, you need to give due consideration to the basic nature of the business. However, the more variable-length columns in the tables, the less precise will be the result of these calculations. This approach may work fairly well for databases with relatively small number of the tables.
0 Comments
Leave a Reply. |