When should I use a Local Database versus the VPM to manage URL lists?


<< Back to Knowledge Search

Solution

Overview

There are two ways to manage custom content filtering categories that contain lists of manually added URLs:

  •     The Visual Policy Manager (VPM): Create an Add Request URL object and enter the lists.
  •     Use a local database.


Both methods are effectively equivalent for URL lists of typical size. When deciding which solution best suits your environment, consider the following:

  •     A large list of locally-categorized URLs is more easily managed in a local database, which is a separate file from policy. Managing more than a few hundred URLs in the VPM can become cumbersome. For extremely large lists (more than 100,000 URLs total), the local database performs more efficiently.
  •     If separation of responsibilities and privileges is required, local database updates can be managed by a user who does not have access to the ProxySG appliance. The installation of the updated database can then be done by a ProxySG appliance administrator. Updates to categories in policy must be performed by a ProxySG appliance administrator.
  •     Because defined categories must fit into memory, a high-end limit exists. Technically, a local database is limited on by disk space; however, lists reaching up into the millions might cause performance issues.
  •     Managing a local database requires a Web server to host the database file. If this is not a preferred deployment scenario, use the VPM.

 

Cause
Resolution
Workaround
Additional Information
Bug Number
InQuira Doc IdFAQ1647
Attachment

Article Feedback

Hide Properties
First Published      10/01/2014
Last Modified      10/01/2014
Last Published      10/01/2014
Article Audience
Product      ProxySG 210, ProxySG 300, ProxySG 510, ProxySG 9000, ProxySG VA
Software      SGOS 4.3, SGOS 5.4, SGOS 5.5
Article Number      000015715
Summary     
Was this helpful?
Comments:
 
Previous MonthNext Month
SunMonTueWedThuFriSat