UNCONDITIONALLY clause
If you are the only connection to the database server, you do not need to use UNCONDITIONALLY. If there are other connections,
the database server stops only if you use the UNCONDITIONALLY keyword.
Cloud note: This statement is not supported on tenant databases in the cloud.
You can only use database-server-name in Interactive SQL only. If you do not execute this statement from Interactive SQL, the current database server is stopped.
By default, the database server is not stopped if there are other connections to it. If the UNCONDITIONALLY clause is used,
the database server is stopped even if there are other connections to the database server. If the STOP SERVER statement is
executed on a client connection and the server successfully shuts down, a communication error occurs.
The STOP SERVER statement cannot be used in stored procedures, triggers, events, or batches.
STOP ENGINE is accepted for compatibility reasons, but is deprecated.
The permissions to shut down a server depend on the -gk setting on the database server command line. The default setting is
all for the personal server, and DBA for the network server.