Hi there guys,
Hope someone can help with this issue.
The stored procedure "MTIS_Threat.analyzeThreatAssetCoverage" is filling up our TempDB log quite extensively. What query is causing this in EPO? Can this be fixed somehow?
Description of the code:
This procedure will reconcile MTIS Threats, ePO Assets with VSE, VIL, and HIPS
and determine the mitigation coverage for the asset
Solved! Go to Solution.
Any time you run your mra analysis task, you'll see your temp db and your log files go way up... Basically it is building a datamart every time you run the product. It is one of those thing you have to plan your disk space around on sql, there is now way around it.
The capacity planning guide for 2.6 is here:
I
t is in the product guide for 2.7
I had a look at few of the server tasks that might cause this, my suspicion would be the following tasks:
MRA Rollup: Roll up Risk Advisor Data
MRA: Data Import
Why would it be doing this? How can this be fixed?
These tasks (and I'm assuming procedures) look like they belong to Risk Advisor, which I'm afraid I'm not familiar with. I would try the Risk Advisor forum - hopefully they will be able to help. (Unless a user here has experience, which is always possible, of course )
Regards -
Joe
Thanks Joe. Just moved the discussion to the Risk Advisor section. Does anybody maybe know what is causing this?
Any time you run your mra analysis task, you'll see your temp db and your log files go way up... Basically it is building a datamart every time you run the product. It is one of those thing you have to plan your disk space around on sql, there is now way around it.
The capacity planning guide for 2.6 is here:
I
t is in the product guide for 2.7
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA