As with the application, the database will require menu-driven scripts that allow it to be shut down and started up. The database should never be forced down unless it is absolutely necessary, because this will cause it to perform recovery operations on startup, to clean up any jobs that were running when the database was shut down. This could take a long time if some large long-running jobs were aborted in the process. One common problem with shutting down a database is getting all the users connections logged off. It is not uncommon for users to leave connections running and forget about them. Scripts will be needed to find these connecting processes and kill them.