Migrating the internal database to an external database

Prev Next

The Database Security server comes bundled with an efficient in-memory back-end database. The database is provided for convenience and should only be used while evaluating Database Security. The existing database should be replaced with a commercial database. For production deployments, separate MSSQL or Oracle database must be used to serve as the back-end database. The back-end migration tool is used to migrate the internal database to the external database.

Database Security supports the use of following external database:

  • MSSQL 2008 up to 2016.

  • Oracle versions 11g and later.

A simple CLI command is used to migrate the database. The back-end migration tool is used to migrate the internal database to the external database and it supports these options:

  • Migrating the internal database to the external database. If at any stage, you revert to the internal database, the data stored on the external database is no longer accessible to the Database Security server.

  • Changing the password used to authenticate the server to the database.

The migration procedure varies based on the database types (Oracle or MSSQL). When migrating to an external database, any existing data is automatically moved from the internal database to the external database when it is created.