Efficient management of multiple databases on one server

Setting a single database for each instance or server makes database management more convenient. However, this will soon increase the cost of your database solution because you need to purchase a new server or a new SQL server license for each database you want to host. To cope with this expensive setting

Setting a single database for each instance or server makes database management more convenient. However, this will soon increase the cost of your database solution because you need to purchase a new server or a new SQL server license for each database you want to host. To cope with this expensive setting

Each instance or each setting can make management more convenient. However, this will soon increase the cost of your database solution because you need to purchase a new or new SQL server license for each database you want to host. To cope with this expensive setting, people generally host multiple databases (that is, multiple applications) on one server or instance ). Although this will reduce the cost of hosting all these databases, it increases the complexity of managing these systems as you now have to handle multiple service-level protocols and maintenance windows.

When you decide to host multiple databases on the same server, the first thing you need to consider is whether these systems have complementary maintenance windows. If one system cannot slow down or go offline at night, and the other system cannot slow down or go offline during the day, these systems are not suitable for sharing one server, you do not have an effective maintenance time window when you need to patch the system or make the system offline for other reasons.

The next deciding factor you need to examine is the service-level protocols of these systems. Systems that require 99% boot time can be arranged together, because you may create a more powerful environment for these systems (maybe cluster solutions) than non-important task systems. This saves you extra costs because you do not need to purchase any high-end systems. Systems with higher service-level protocols may have the same maintenance time window. Therefore, these systems complement each other at the beginning.

　　Database Backup

Backup is another key issue that needs to be solved when multiple databases are hosted on one server.

Each database has its own backup requirements. Backing up a database may be the most complex task that can be executed on the SQL server. This is not because this backup requires a lot of CPU and memory resources (the resources occupied by this task are usually very low, unless you compress the database during Backup ), instead, backing up a large database requires a lot of hard disk resources.

During full backup, the entire database must be read from the hard disk. If your hard drive system is very busy, this backup will cause serious performance degradation. The best solution for this backup is to choose the right time. You can also find a third-party tool that allows Database Backup compression while backing up. Because this will increase the CPU workload on the SQL server, it usually takes only a small amount of time to complete the backup, because there is little data to be written into the backup device.