It is possible to select a Mimer SQL database that has been set up, using the Mimer Administrator, as a local database on the specified network node.
After you specify the network node, and select a Mimer SQL database, up to date status information is displayed describing whether the database is running or not and if logins are allowed.
You can select from the following functions:
| Operation | Description |
|---|---|
| Start | This starts the selected database and automatically enables logins. You can only select databases located on the node you have specified. |
| Enable Login | This allows logins to the selected database. You can only select databases located on the node you have specified. |
| Disable Login | This blocks additional logins to the selected database. You can only select databases located on the node you have specified. The database will remain running, but new connections will be refused. |
| Stop | This shuts down the selected database. You can only select databases located on the node you have specified. |
Some of the functions may not be available, depending on the status of the database (e.g. you cannot select Start for a database that is already running).
The database status information is updated dynamically so it will reflect the outcome of any function selected. Any error information relating to unsuccessful attempts to alter the state of a database will also be displayed. Error information will also be recorded in the Windows Event Log and can be inspected using the Windows Event Viewer or the Microsoft Management Console.
When you start a database, Mimer Controller checks to see if the services Mimer TCP and Mimer Named Pipes are running. If they are not running, and are set up for Automatic start, they will be started.
Note that, by specifying different nodes in the network, you can control databases that are local to machines other than the one you are using.