Showing results for 
Show  only  | Search instead for 
Did you mean: 
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 1 of 1

Content Security Reporter Database is huge. How to manage the SQL Database (The Answer)

A while back I was amazed how little traction I got from posting this same question. 

We finally got this under control. I wanted add this so others using the combo of products for Web Gateway reporting and facing this same problem can see what seems like the fix.

Summery of the issue. We had rediculous DB growth generating to the SQL DB for the CSR Reporting. 

We had finally cut the reporting to only 3 weeks and the DB had climbed to just under a TB. 

(Of course we had done all the normal stuff with DB maint and settings for the Report server in ePO).

Finally, I got with Support and we worked through 2 things that did the trick.


1. Look at the Dashboard for CSR: Web Activity

The report to the right "Top Web Bandwidth Consumption Usage by User and Site" tells the story.

The first half a dozen entries for us were interactions with the site "" 

Turns out there are two dumb things with Adobe products.

1. They seem to constantly call back looking  for Updates and the default setting is turned on.

It can be turned off. Which we did. But we still had millions of hits up to the site.

2. Adobe cloud produces are always attempting to go to the site to Validate licensing.  From Adobe, this is not something that can be turned off. 

So in a nutshell you end up with some choices to make.

1. Do you Whitelist the site? (Security-wise a risky move and even if white-listed there is probably too much noise from it).

2. Find user machines with instances of the product and remove it if it is not needed, or sanctioned.

- A report can be run in ePO to find the computers attemting to hit the site. 

3. Stop reporting the site requests to the site.

This is pretty cool if you don't have an issue with allowing some data to go unreported. (For Strict auditing this is a problem).

Anyway, you can create a simple rule in the MWG Log Handler / Access log for a does not match list of sites to not do reporting for. (If you are not an expert on your MWG, I would suggest a call to support on how to do this correctly).

Not a one fix does it all, but the combo drastically reduced our DB size so we could reasonably increase our retention to 60 or 90 days.

There you go. Thanks




You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from product experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by employees.
Join the Community
Join the Community