Database tuning involves various queries and applications. The tuning function can be applied in the disk usage, memory as well as to access the database as a whole. Therefore, you are required to know about all the application requirements of the database tuning.
OLTP or Online Transaction Processing: When you are looking for the data entry operation in any organization, you are surely looking out for the OLTP. This application is highly adaptable with the frequent changes of data. As the data user base generally remains large in volume, all the new updates and the inserts can be smoothly done through the Online Transaction Processing. They are mainly used for the online ticketing functions or the timesheet entry systems and many other applications where large volume of data is used. The accuracy cannot be compromised though the data is highly volatile in nature. As re-entering and overwriting the data takes place very frequent, there are mechanisms that can be updated accordingly. The clusters and indexes must be managed optimally so that the database never gets affected. There can be a minimum number of the indexes and the clusters need to be shaped carefully so that the data tables are always sufficient to hold on the data. You can surely avail the remote DBAsupportathttp://www.remotedba.com to learn more about the usage and the applications. The data normalization function can ease out your maintenance of clusters and indexes.
Decision Support Systems: DSS or the Decision Support System can be used to generate information and reports. Though the DSS can be combined with the OLTP to perform the database functions, they are designed differently from OLTP. Their mechanism can support small volume of data which is very unlikely with OLTP. The data passes from the OLTP to the DSS through the branch schedule process. If accessing the query is required, the DSS can support new data insert or update in its system very smoothly. The number of options available for the performance tuning can be large as the DSS function takes place in the batch schedule. The DSS may accumulate the data tables into a special table space with a read-only access memory.
Client/Server Network: As the name implies, the network surely includes both the components client and server. It is the process of a proper communication with one another between the client and the server. The client consists of all the user process and the graphical user interfaces. The server, in this particular case, Oracle database consists of memory, disk usages and all the back-end processes. The network interface helps both the components to make the flow of the information back and forth. The architecture of the Client/Server can be generated through the SQL* Net where it can act as the listener or the receiver of the data. The database servers can have a single receiver or a multiple receiver also known as the Multithreaded (MTS) option.
Temporary Systems for Specific Needs: There can be some temporary systems that are always useful for specific needs. There can be some specific time where the data usage doubles the normal days. Some initialization parameters which help in re-entering the log usage will be beneficial in this case. The init.ora file can easily be altered for changing the configuration and for reflecting them on the required parameters. After the complete use the scripts can be reversed and the database can be restarted with the init.ora folder.
Thus database tuning can be done with the Online Transaction Processing, Decision Support System, and client/server system as well as when some specific requirement of application occur. Tuning can surely ensure the configuration of the data maintenance in a very short period of time.