Skip to main content

Purge Publish Transaction Script

Image
By
Ok, it's time to do some maintenance and performance tuning on your Tridion CMS. One of the things you should keep an eye is the size of the Publishing Queue. This can grow quite large over time depending on the amount of publishing going on daily.

Tridion comes with a very handy tool -- the Purge Tool, which allows trimming the size of the Publishing Queue. I won't go into what the tool can do; there is documentation for that.

The following little script is perfect to run inside a Windows batch script and schedule it to execute periodically. In its current state it deletes Publish Transactions that completed more than 1 year ago relative to today's date.

@echo off
set /a LastYear=%DATE:~10,4%-1
set OneYearAgo=%LastYear%/%date:~4,5%
echo OneYearAgo=%OneYearAgo%
echo TRIDION_HOME=%TRIDION_HOME%

@echo off > "%TRIDION_HOME%bin\purge.xml" & setLocal enableDELAYedexpansion
for /f "tokens=* delims= " %%a in (purgeTemplate.xml) do (
    set str=%%a
    set str=!str:XXX=%OneYearAgo%!
    >> "%TRIDION_HOME%bin\purge.xml" echo !str!
)

cd "%TRIDION_HOME%bin"
PurgeTool.exe purge.xml /Purge

For the worth, it cool noticing how ingenious the last year's date is constructed, then how the find and replace is taking place in the template file.

The batch script makes use of the following template file, which simply offers all default values for the purge job. The cutoff date is give by pattern XXX:

<XML>
    <Settings>
        <LoggingDirectory>C:\Tridion\log\</LoggingDirectory>
        <LogFilePrefix>Purge_</LogFilePrefix>
        <Items Purge="false">
            <Keep>5</Keep>
            <DaysToKeep>0</DaysToKeep>
            <Recursive>0</Recursive>
        </Items>
        <ProcessHistories Purge="false" Before=""/>
        <PublishTransactions Purge="true" Before="XXX">
            <State Purge="true">Success</State>
            <State Purge="true">Failed</State>
        </PublishTransactions>
    </Settings>
    <Scan>
        <Root Purge="False"/>
    </Scan>
</XML>

In order to execute the script, simply call the batch file from Windows command prompt or within a Scheduled Task. The script requires the environment variable TRIDION_HOME be set. Obviously, run the script on the Tridion CMS server.

Labels:

Comments

Anonymous said…
Hi, the batch script is works perfectly. But , i want to purge all the logs queued by specific user , is there some way to provide the user name ,so that i can script it to delete all the successfully published logs by that user .
24 April, 2015 12:06
Post a Comment

Popular posts from this blog

Scaling Policies

By
This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the
Post a Comment
Read more

Toolkit - Dynamic Content Queries

By
This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio
Post a Comment
Read more

Running sp_updatestats on AWS RDS database

By
Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as
1 comment
Read more