Vacumming Question

We have SQL NS 2005 with our ADF with the following setting:

<Vacuum>
<RetentionAge>P7DT00H00M00S</RetentionAge>
<VacuumSchedule>
<Schedule>
<StartTime>05:00:00</StartTime>
<Duration>P0DT02H00M00S</Duration>
</Schedule>
</VacuumSchedule>
</Vacuum>
Shouldn't this only be retaining data for 7 days, which perhaps I should remove defined RetentionAge since that is supposed to be the default according to BOL.
We have rolled this out in November, but I am not seeing any old data getting cleaned up.
Is it my configuration setting or a bug? I have run exec nssnapshotapplications and it shows it is running on the scheduled basis. I just want to get some clarification before making a change for our production environment.
[982 byte] By [AndyWilbourn] at [2008-2-25]
# 1
I just looked at the output again from the said procedure and saw that it last ran the day we set it up. That would explain why nothing has been cleaned up. I will continue to look if there is something I missed to get it to run, but thought I would post what new things I have found.
AndyWilbourn at 2007-9-9 > top of Msdn Tech,SQL Server,SQL Server Notification Services...
# 2
Are there any events in the Windows Application Log? Have you tried initiating Vacuuming manually to see if that works?

--
Joe Webb
SQL Server MVP
http://www.sqlns.com

~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811

I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)

JoeWebb at 2007-9-9 > top of Msdn Tech,SQL Server,SQL Server Notification Services...
# 3

I can run the vacuuming manually and it works. I do not see any entries in the event log noting problems. Would I have to turn up the debugging level to get that?

Thanks for your support Joe.

AndyWilbourn at 2007-9-9 > top of Msdn Tech,SQL Server,SQL Server Notification Services...
# 4
Did you ever resolve this iuuse?
TimBederka at 2007-9-9 > top of Msdn Tech,SQL Server,SQL Server Notification Services...
# 5

You'll probably want to set the vacuumer to verbose logging until you resolve this. Check out

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlntsv9/html/ba1164a1-b965-48ff-9b86-da92f519be54.htm

for more info on updating the logging levels for various components.

HTH...

Joe

JoeWebb at 2007-9-9 > top of Msdn Tech,SQL Server,SQL Server Notification Services...

SQL Server

Site Classified