Some space in the data files is allocated and used by the database objects however, there is usually some unallocated space. In the nutshell, the database files are just the containers for the data. I would also focus on the data files only – troubleshooting and reducing transaction log size is the different topic.
WAYS TO SAY SUPPORTED CLIENT BASE RESUME CODE
Some of them are fully transparent to the client applications others require regression testing and/or code refactoring. Today, I am going to discuss several methods that can help in reducing database size. Plenty of things that can help to meet strict RTO requirements and smaller database size definitely helps. Think about designing Disaster Recovery (DR) strategy. Even though size reduction is rarely the primary objectives of such projects, reducing the size often helps to achieve other goals. The projects when you have to reduce the size of the databases are very common. However, on the bare minimum, there is always the storage cost. It is entirely possible that applications deal only with the fraction of the data stored in the database and, therefore, even mediocre server can handle the load. There is, of course, very subtle difference between the size of the database and size of the active (hot) data. Large databases usually require powerful hardware to run. Professionals, who can design nontrivial solutions in all areas – architecture, availability, maintenance, performance tuning, to name just a few. You need to have highly skilled professionals in the team. Those databases are more expensive to support and maintain. The problem, however, is that the large databases are not good for the customers.
Customers usually understand amount of work involved in such projects. Last but not least, customers with multi-terabyte databases do not have problems with multi-kilodollar invoices. They are fun to deal with they give you priceless experience and look cool in your resume. As the database professional, I like multi-terabyte databases.
0 kommentar(er)
