What about the MSSQL performance? what do you have configured for that? You might need some additional RAM to run the extended queries with more a few months of data
When we live, the minimum recommended database was at least cores and at least 64 GB of RAM for the small environment. Medium doubled the RAM and Large went to 24/256. We are a much larger environment (our DB is multi-TB) and we ran 128GB x 16 core database with minimal issues. I would look at adding resources to the DB server as that is where the bulk of the processing is done.
In our case, what is the recommended specs for all servers (CSR, epo, DB)? As McAfee Support Team ask me to use external DB and use separate servers for epo and CSR and this does not solve the problem
I can't speak for McAfee, but it appears that the CSR Server is sized right and configured right or the inserting of log data would be painful. I suspect the issue is with resources on the database.
I would recommend getting the database to at least 10 cores and either 64 or 128 GB of RAM to see if that solves the problem. That would be a small to medium configuration for the DB.
Per the 2.6 installation guide: The amount of time it takes for the schema to update depends on the size of your database. For example, a database with 50 GB of data takes about 5 hours to update.
So it could take 1 hour per 10 gb of data.
I am also going to move this over to the group that supports CSR, as they can probably answer your questions better.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?