Article Content
Article Number | 000033814 |
Applies To | RSA Product Set: ECAT RSA Product/Service Type: ECAT RSA Version/Condition: 4..0.x,4.1.x,4.2.x Platform: Windows Platform (Other): SQL 2012, SQL 2014 |
Issue | This is a how-to article dedicated to performance enhancements and otherwise advice on tuning the performance of the ECAT database. |
Resolution | Recommendations Database Performance/Tuning It is necessary to understand what the minimum recommendations are and to remember that disk space is heavily influenced by the flow of data, along with most other factors in NetWitness Endpoint. For instance, if the QueuedData folder is inaccessible to the database, files will build in the folder over time, potentially consuming enormous amounts of space since agents will continue to check in with the console server and queue up data. So to start, it is good to begin with the recommended minimum specs for the database starting with the below:
![]() These are not hard or fast rules. Requirements depend on the size of the environment (number of agents, database hardware, etc.) and vary over time; this is an example of a good rule of thumb for a typical setup. Below are suggestions to assist in tuning the database for better performance:
## Starting with Versions 4.1.2.x and above, BIT9 Database has been replacing by File Reputation Service https://community.rsa.com/community/products/netwitness/blog/2016/06/23/big-changes-happening-in-rsa-ecat-412-now-available |
Notes | SQL Server Best Practices https://technet.microsoft.com/en-us/library/dd758814(v=sql.100).aspx Below are the BPM query and Batches queries for reference |