Database Reference
In-Depth Information
size of a tablespace. Moreover, we can also estimate the
frequency of data growth in each table e.g. while in analysis
phase we can ask a worker in that department how many people
you add or sign-up for service per month and if he/she say 10
then keeping in mind address_book table.
The formula to find out estimated frequency of growth of table
would be as follows.
Table's Estimated Frequency Of Growth (Bytes) Per Month =
(Number Of New Records Insertion per Month) X (Size Of
Record)
In our scenario it will come out to be (10 X 220) 2200 bytes per
month or in other words 2.2 KB (Kilo Bytes).
The sum of all the
estimated frequencies of growth of all the tables within a
department will give us the estimated frequency of growth for a
tablespace that we will create for that department. Following on
the same lines the sum of all the frequencies of growth of all the
tablespaces with the database will give us the frequency of
growth of database.
Same applies to figuring out the initial size
of the database i.e. sum of initial estimated sizes (bytes) of all the
tablespaces gives us the size of the database. Whereas the size of
the tablespace is the sum of initial estimated sizes of all the
tables within that tablespace or in other words department.
We can very easily roughly estimate the maximum number of
connected user at any given instance if we know the number of
employees that the company has and the number of clients
and/or customers, accessing the Oracle Database.
The purpose of finding out the rough estimation of maximum
number of concurrent users accessing the Oracle Database is to
come up with the decision whether “Shared Server” mode is
more preferable for us or “Dedicated Server” mode.
Search WWH ::
Custom Search