Was this helpful?
Using Multiple Databases
X100 fully isolates activities from various databases. Each database has its own storage system, buffer pool, and query memory pool. As a result, multiple databases running at the same time can lead to high resource consumption. For optimal performance, we strongly recommend that only a single database be used on a machine. Consider using different schemas to isolate multiple applications on the same database.
If you do plan to use multiple databases on one machine, we recommend that you reduce their resource consumption, mainly memory usage (max_memory_size and bufferpool_size parameters).
Closing an Active Database
If no more activity for a particular database is expected, you can recover system resources by terminating the X100 Engine for that database. You can either terminate the engine forcibly, or specify that it should stop when no active sessions are using the database.
To stop the X100 Engine immediately
Issue this statement in a SQL client connected to the database you want to close:
CALL X100(TERMINATE)
Note:  This may interrupt running queries and cause them to return an error.
To stop the X100 Engine when no other sessions are using that database
CALL X100(TERMINATE_IF_IDLE)
and then exit your SQL session. The X100 Engine will exit when no other sessions using that database are active.
Last modified date: 03/21/2024