Skip to main content

What is syspolicy_purge_history

When  we  installation or upgrade Sql Server  from a previous version  into 2008, by default a job will be created syspolicy_purge_history.

 
What does it do?


Sql Server 2008 introduced a new feature called Policy Based Management. 

For example, one could define a policy that says all tables must have a clustered index. 

Once defined, the policy can be evaluated against targets to check for compliance. Each evaluation of compliance will be recorded in below tables :-
1. msdb,
2. syspolicy_policy_execution_history_details_internal, 
3. syspolicy_policy_execution_history_internal, and 
4. syspolicy_policy_category_subscriptions_internal 

The evaluation condition is built on top of object facets, which is predefined by Microsoft.The purpose of that job, syspolicy_purge_history, is to remove records in those tables to maintain so it does take up space unnecessarily


Happy Readding.
@Sumnjha

Comments

Popular posts from this blog

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. ·          23 May 1995 - First internal release ·          Year 1996 - Version 3 o     Simple CRUD operations o     January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o     production release 1998, from www.mysql.com ·          Year 2002 - Version 4 o     MyISAM o     unions o     Tracking o     B-trees o     s...

How to recover msdb database from suspect mode

 It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..

How to setup automated export on google cloud sql

We can do backup and restore on instance and DB level both. on-demand backup and automatic backup are possible at instance level only which we can configure Google Cloud Console. Database level there is no options and features available for full and differential backup like SQL server in cloud SQL database. We can do this task with Export feature this is similar to full backup and this we can do from console or portal. If we want to do automated DB export (full backup) then we should design ourselves with the help of services . Google provide some services like Google Function and Scheduler which we can use for this purpose as look like following architecture. Here is following steps which we can use to setup Create a bucket in Google Cloud Storage. Create Cloud Function to export a Cloud SQL database Grant Permission for the Cloud Function to access Cloud SQL export Test out the Cloud Function Create Cloud Scheduler Job to trigger the Cloud Function once a week  For detail or step...