Solution to online SQL Server Service Failure

Two days ago, I made a very serious mistake. When I was observing the SQL Server database time, due to the adjustment of the service, I accidentally restarted the SQL Server service. Maybe everyone felt this was okay, however, for an online DB that supports tens of millions of PVS a day, the problem is serious. The SQL Server service cannot be started after it is stopped. It is too speechless. Because the site traffic is too large, the SQL Server server is online and cannot be restarted, you can only stop IIS from the three sites accessing this dB, and then restart the DB server. Restart the DB server.

You should note that you can handle the problem that the online dB service cannot be started:

1. Stop all web IIS accessing this DB

2. Restart the DB Server

3. After the DB server is restarted, you cannot immediately switch the links of all sites to this dB. You must first switch back a site with a small access volume and then switch it one by one. The standard is to look at the memory of the DB server. Because the DB is very memory-consuming, the table structure, connection string, query optimizer, and user authentication information must be cached in the memory in the early stage, therefore, it is forbidden to direct large traffic to the newly restarted DB server.

4. Through this error, it is found that the Web site accessing the DB through the Intranet must be restored first, while the access from the Internet is a little slower.

Fortunately, the boss did not say anything. Be careful when operating online databases.