This section applies to standard solidDB® only. If you are using solidDB® with shared memory access (SMA) or linked library access (LLA), see the solidDB® Shared Memory Access and Linked Library Access User Guide for instructions on how to stop the solidDB® SMA or LLA server.
Procedure
You can shut down the solidDB® in the following ways:
▪To shut down solidDB® programmatically from an application, for example, using solidDB® Remote Control (solcon) or solidDB® SQL Editor (solsql):
1 Prevent new connections to solidDB® by issuing the following command:
ADMIN COMMAND 'close'
To revert the effect of the close command, issue the ADMIN COMMAND 'open' command.
2 Exit all users of solidDB® (except the current connection) by issuing the following command:
ADMIN COMMAND 'throwout all'
The throwout all command does not wait for open transactions to finish; it rolls back all open transactions.
3 Stop solidDB® by issuing the following command:
ADMIN COMMAND 'shutdown'
To shut down solidDB® using a single command, issue the following command:
ADMIN COMMAND 'shutdown force'
The shutdown force command performs the same operations as close, throwout all, and shutdown.
▪In Windows environments, right-click the server icon and select Close.
▪In Windows environments, if you are running solidDB® as a service, you can use the commands net stop or sc stop through the Windows system services.
Results
All of the above-mentioned shutdown mechanisms start the same routine; all buffered data is written to the database file, cache memory is freed, and the server is shut down. The server shutdown can take a while since the server must write all buffered data from main memory to the disk.