After you have crashed a database server, there are many important steps that need to be taken in order for the server to be operational again.
The Following Lists 10 Things That Any Good DBA Should Do After They Have Successfully Crashed Their Database Servers:
Below we have provided you with the 15 things that you need to do after crashing a Database Server. Let’s discuss them:
1. Panic
You should go into panic mode immediately. Shout to everyone in the vicinity. Cry. Pull out your hair.
2. Call The Helpdesk
Call the helpdesks of both Microsoft and Oracle to have them reset their licensing servers/databases which can be used to re-activate any of your software on your server(s).
3. Tell Everyone You Know That You Just Crashed A Database Server
You should post this to all social media sites or discussion forums that you are part of or subscribe to. Also, tell everyone at your local I.T group/computer club/user group.
4. Blow Off Work For The Rest Of The Day
After you have successfully crashed a database server, there is no reason to show up to work the next day.
5. Call A DBA Friend Or Two
If you know any other DBAs, now is a good time to call them and tell them that you just crashed a database server.
6. Make Sure None Of Your Users Are Still Connected To The Crashed Database Server
You should check this by running a query along the lines of:
If you have more than 1 result, then a user is still connected to the server and this must be rectified immediately before you can continue on with your efforts to bring the database back online.
7. Unplug The Crashed Server
You should unplug the crashed server from all power sources. If it is a blade, make sure to remove it from its enclosure.
8. Reboot The Entire Datacenter
It has been found that crashing a database server can cause other servers in the same data center/rack/floor to crash as well if they are not rebooted. To prevent this from happening, you should reboot everything.
9. Pick A Random Port Number For The Database To Run On
As stated in point 7 above, it has been found that if a database server is not running on a unique port number that its services will interfere with any other servers on the network. In order to resolve this, you should pick a random port number for the database to run on and make sure all users/applications/software is configured to use this port.
10. Unplug The Crashed Server
You should unplug the crashed server from all power sources. If it is a blade, make sure to remove it from its enclosure.
11. Plug The Crashed Server Back In
You should plug the crashed server back into both power and network sources.
12. Reboot The Entire Data Center (Again)
See point 8 above.
13. Try To Login/Connect To Your SQL Server Using SSMS On A Different Machine, But Fail
You should do this immediately after you have plugged the SQL Server back into your network.
14. Plug Your Crashed Server Into Its Own Private Subnet/VLAN With No Internet Access
By doing this, you will ensure that if someone else has also successfully crashed a database server, they will not be able to do so again because their server will be on another subnet/VLAN which will be inaccessible on your network.
15. Call Microsoft/Oracle
Again to see if they can reset their licensing servers which you can then use to re-activate any of your software on this server.
Read More: Seven Steps To Starting A Transport And Logistics Business
FAQs:
A: No.
A: There seems to be a bug in this particular technology that causes other servers to crash due to not rebooting the entire data center.
A: This is an indication that there may be more than one bug in this technology and you should discontinue using it immediately.
A: Yes. There is nothing more pathetic than an amateur database administrator who can’t even crash their database servers properly.
A: You are just not doing it right. You should try again.
A: Try again later.
Conclusion:
So there you have it. 10 easy steps to successfully crashing a database server the next time one of your users accidentally runs a query you have already told them not to run.