This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

DPA Repository Database Size Growing

FormerMember
FormerMember

Hi all,

We have been using DPA since this year March, and we realized the repository database size has been growing.

Based on the guidebook that we have followed, it was said that for a high activity database instance, the disk space required is 5GB.

We are monitoring about 6 instances, and so far we have been allocating about 200GB space for it.

Is there any purging job being setup for this repository database?

Parents
  • FormerMember
    0 FormerMember

    Thanks gcp and jaminsql for the reply!

    Yes gcp, I am using the SQL server as the repository. The space is consumed by the database files. The log space looks alright.

    This is the screenshot of the settings, and yea, the number of days of data history is set as the default values of 30 days.

    clean_details.jpg

    However, since I have set up since March this year, it shouldn't have been keep increasing? For it will do up the cleaning job every 30 days...?

    May I know how many days you guys have set the value for this CLEAN_DAYS_OF_DETAIL?

  • Default 30 days here...  20 monitored instances, ~90GB data file for SQL Server repository

Reply Children
No Data