Purging the CMS Database

When items are deleted from a Deleted Items container, they are flagged as such in the appropriate tables in the database, and therefore the Site Manager doesn't display them anymore. For the same reason, the deleted items are not accessible from the PAPI. However, the deleted items' data is not actually deleted from the CMS database at this stage.

The deleted items' data is purged from the CMS database tables by a background SQL Server Agent job that is created when you populate the database in the DCA. By default, the job is called BGP-<CMS database name> and is scheduled to run daily at 1 AM. To access the job, open SQL Server Enterprise Manager and then open Microsoft SQL Servers > SQL Server Group > <server name> > Management > SQL Server Agent > Jobs, as shown in Figure 16-33.

Figure 16-33. Background purging job


The job consists of four steps performed in the following sequence (Figure 16-34):

  1. Process expired pages.

  2. Purge content for deleted pages.

  3. Update gallery-based resources.

  4. Purge data for deleted resources.

Figure 16-34. Background purging job default steps


The first step deletes the expired postings; it is not enabled by default. To change this and other settings, right-click the job in the right pane and select Properties, and then go to the appropriate tab, as follows:

  • The General tab allows you to the change job's ownership, category, and description. The job is enabled by default; to disable the job, clear the Enable box in the General tab.

  • The Steps tab provides the ability to change the sequence of steps, add new steps, or run each step individually if necessary (Figure 16-34).

    To enable the first step deleting expired pages select step 1 from the "Start step" list.

  • The Schedules tab allows you to modify the default schedule for the job.

  • The Notifications tab provides the ability to set up actions to perform on the job's completion.

Background job events are logged in the SQL Server Agent log file <SQL server installation point>\MSSQL\LOG\sqlagent.out. You can view the SQL Server Agent error log by right-clicking the SQL Server Agent node and selecting Display Error Log.

NOTE: In certain situations, you have to manually start SQL Server Agent. For example, when you stop SQL Server, SQL Server Agent is stopped as well. However, when you restart SQL Server, SQL Server Agent is not restarted automatically. Another example is when SQL Server is installed on a remote computer. The DCA that is installed locally cannot start SQL Server Agent on a remote machine. In both scenarios, to enable the background purging of the CMS database, you must start SQL Server Agent manually.

Microsoft Content Management Server 2002. A Complete Guide
Microsoft Content Management Server 2002: A Complete Guide
ISBN: 0321194446
EAN: 2147483647
Year: 2003
Pages: 298

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net