Deep Security 12 FR has reached end of support. Use the version selector (above) to see more recent versions of the Help Center.
Migrate Microsoft SQL Server Express to Enterprise
Microsoft SQL Server Express is supported in very limited deployments (see Microsoft SQL Server Express considerations for details). If you are using a Microsoft SQL Server Express database but find its limitations too constricting, you can migrate it to Microsoft SQL Server Enterprise edition, or another supported database.
To migrate to Enterprise:
-
Stop the Deep Security Manager service so that it stops writing to the database.
Deep Security Agents will continue to apply their current protection policies while the manager is stopped. Events will be kept and transmitted when Deep Security Manager returns online.
- Back up the database(s).
-
Back up the database connection settings file:
[Deep Security install directory]/webclient/webapps/ROOT/WEB-INF/dsm.properties
- Move the database to the new database engine. Restore the backup.
-
Edit dsm.properties to connect to the migrated database:
database.SqlServer.user
database.name
database.SqlServer.instance
database.SqlServer.password
database.type
database.SqlServer.server
If using the default instance, you can delete the
database.SqlServer.instance
setting.You can enter a plain text password for
database.SqlServer.password
; Deep Security Manager will encrypt it when the service starts, like this:database.SqlServer.password=!CRYPT!20DE3D96312D6803A53C0D1C691FE6DEB7476104C0A
- Restart the Deep Security Manager service.
-
To verify that it has successfully reconnected to the database, log in to Deep Security Manager.
Existing protected computers and event logs should appear. As new events such as administrator logins or policy changes occur, they should be added. If not, verify that you have granted permissions to the database user account on the new database server.