Microsoft SQL Server Express considerations

Some deployments might be able to use Microsoft SQL Server Express for the Deep Security Manager database. Important limitations are below. If you think your deployment cannot operate within these limitations, use another supported database instead.

If you exceed the limits, you will experience a service outage and you will need to upgrade to a paid version of Microsoft SQL Server.

Express edition limitations

Microsoft SQL Server Express has a 10 GB maximum database size and other important limits. High load scenarios are not supported by Express. Symptoms can include database connection errors.

Express has a "LocalDB" preset. More configuration may be required to accept remote connections.

Limited number of protected computers

Do not use Microsoft SQL Server Express if your deployment has more than 50 protected computers. More computers' events will cause a larger database which Microsoft SQL Server Express cannot handle.

Multi-node Deep Security Manager, required for larger deployments, is not supported by Express.

Security module limitations

Only Deep Security Anti-Malware and Intrusion Prevention modules are supported with a Microsoft SQL Server Express database due to its limitations. If you require any other protection modules, use another supported database instead.

Minimize the agent size

Remove any unneeded agent software packages from the Deep Security Manager to save disk space.

Database pruning

Security updates and events require additional space in the database. Monitor your deployment to ensure that you stay within the Express databasize size limit. For information on database pruning, see Log and event storage best practices. You may also choose to use the SQL Server settings described in Considerations for the "autogrow" and "autoshrink" settings in SQL Server.