SQL Server deployment options overview - Genetec Mission Control™

Genetec Mission Control™ Deployment Guide

Applies to
Genetec Mission Control™
Last updated
Content type
Guides > Deployment guides
English (United States)
Genetec Mission Control™

You can deploy the SQL Server in various ways depending on your existing system infrastructure and business needs.

SQL Server deployment options

If you are using a licensed edition of SQL Server (like SQL Server Standard, SQL Server Business Intelligence, or SQL Server Enterprise), keep in mind that all databases are managed by Microsoft SQL Server in Security Center. By default, SQL Server is configured to use as much memory as is available on the system.

This could lead to memory issues if you are hosting SQL Server and many roles on the same server, especially on a virtual machine with little memory resources.

For more information on Security Center databases and networks, see Databases.

To protect the Directory database so you do not lose any data you have a few different options:
Option 1
Configuring SQL server cluster
Option 2
Setting up Directory database failover
Option 3
Separate databases for Security Center Directory and Incident Manager roles

SQL database requirements

The SQL Server Express edition included with Genetec Mission Control™ has a database size limit of 10 GB and does not support SQL clustering.

The average size of an active incident in the Incident Manager database is approximately 10 KB. If you have 3000 - 4000 incidents per day, you would need 10 GB of database space with a configuration of 1 year retention period.

The average size of an incident type configuration is approximately 5MB. The largest part of any incident type configuration is the Automation workflow configuration. Each time the incident type configuration is modified, a new revision of the incident type is saved in the system. Each revision approximately takes up 2MB of space. If you have a 100 incident types, you would need 500MB of database space.

If you need a longer retention period or require failover clustering for SQL Server high availability, it is recommended you use SQL Server Standard or Enterprise editions.