Badger TraCS Guides
Database Server
Database Server
The database server is used to house all of the following databases used by TraCS.
Application | Database | Supported Database Types | Use |
TraCS | TraCS_Data |
SQL Server Express 2016 or above (x64 only.)
SQL Server 2016 or above (x64 only.) Both Standard and Enterprise versions are supported. (Preferred Database) SQL Server 2019 or above (x64 only) | Used by TraCS to store all form data. |
| TraCS_Support | Used by TraCS to store all supporting data such as code lists and database queries. | |
| TraCS_Users | Used by TraCS to store all user related data. | |
| TraCS_Logs | Used by TraCS to store all log data. | |
| TraCS_Update | Used by TraCS to store all update data. |
*Although TraCS can use Microsoft Access as its databases in very small agencies, it is recommended that SQL Server Express be used instead. The TraCS Support database is typically installed on each Windows device as Microsoft Access for installation and deployment convenience.
The following is a base set of database server hardware and software requirements to work from. The database server requirements can vary considerably based on the implementation type, load, and many other factors. For example, a centralized statewide implementation of TEG Public Safety Software will require significantly different server specifications than an implementation at a local police department with only a few devices.
Database Server(s)
Operating System: Windows Server 2019 or above (x64 only)
Internet Information Services (IIS): IIS 8 or above
.NET Framework: 4.8
Processor: Quad Core, 3.0GHz or higher
Memory: 16 GB RAM or more
Storage: 50 GB free
Other Database Server Configurations
Depending on the size of the TEG Public Safety Software implementation, smaller agencies could combine the application server with the database server on one server box.
Enterprise agency or statewide implementations may want to take advantage of existing database server clusters or server farms that are already configured for database mirroring, redundancy, and disaster recovery.
Database Storage
In most TEG Public Safety Software installations, the actual database files are stored on the database server. However, in larger agencies, storing the database files in a separate location such as in a storage area network (SAN) is highly recommended. This allows the database files to be put into a routine backup plan and usually provides a mechanism for data redundancy and disaster recovery. However, depending on infrastructure, it has been found that latency issues with SAN implementations has caused MACH performance degradation in some cases.
The data storage requirements of TEG Public Safety Software again can vary greatly by the size of the implementation. Large centralized statewide deployments of all the TEG Public Safety Software modules could easily generate 500GB or more of data a year. Using the MACH bread crumbing feature can significantly add to if not double the yearly data storage amount.
TraCS may be configured to use SQL Server 2008 R2 x64 (or higher; SQL Server 2016 must run in 2014 compatibility mode) or MS-Access as the database in which the TraCS data is stored. You do not need a copy of the MS-Access program; TraCS can store and retrieve the data in MS-Access format without any additional software. Due to the limitations of MS-Access, it is not recommended if you plan to have more than one concurrent user in the office. (Unlimited users in the field are fine.) Please consider using SQL Server or SQL Server Express if you plan on more than one concurrent office user.
Related content
email badgertracs@dot.wi.gov or call 608-267-2096