September 30, 2013 at 4:51 am
Does anyone know where the table core.source_info_internal gets the days_until_expiration value from.
I have an MDW database which has grown to epic proportions.
It looks like the MDW purge SQL agent job which executes the core.sp_purge_data is getting the valid_through date via the core.snapshots view which the purge is based on from the core.source_info_internal - days_until_expiration column. The days_until_expiration value is set to 730 for a number of collections.
I cannot seem to find this value in the Data Collection retention days setting in the SQL agent job which are set to a more manageable no. of days. Could these values have been changed via the agent jobs but not yet persisted to the table until a restart of the agent service is executed?
September 30, 2013 at 5:47 am
The core.source_info_internal gets the days_until_expiration value is set by the collection sets. 730 days is the default for the disk_usage collection and usually this isn't causing too much growth.
In my experience the collections sets "Server Activity" and "Query History" are responsible for most of the data and the default retention period for these is 14 days.
You can change the retention period by opening the properties of an colletion set.
[font="Verdana"]Markus Bohse[/font]
September 30, 2013 at 6:57 am
Ah, I get it now.
I thought that editing the Data Collection set in the MDW instance would change for each instance that is being monitored (I'm also monitoring my MDW instance too). When in fact I will need to go to each instance and change the data collection set from there.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply