Well, your timezone certainly makes like a bit more simple from this
point of view. :)
Anyway, your theory may very well be correct. Tomorrow morning, check
the result of this T-SQL statement to see how many events and
notifications were removed during vacuuming.
SELECT * FROM dbo.NSVacuumState
BTW - You can also run the
stored procedure from the instance database to essentially get the
If you not cleaning as much as you'd like, you can specify a couple of
vacuuming periods - one before the backups and another after the
But, I wouldn't really expect the backups to interfere with vacuuming
if they are running simultaneously - other than further taxing the
system resources and making things run a bit slower.
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On Thu, 15 Sep 2005 07:07:07 -0700, "J" <[email protected]>
>No problem, we're in Southampton, England. So we shouldn't need to adjust
>the time :)
>I have a thoery as to why it doesn't look like it's cleaning down. It's
>taking approx 1hr to clean down 200,000 events in our system. I'm wondering
>if it is working, but we're generating more than it can clean down in the
>specified time interval.
>What do you think?
>"Joe Webb" wrote:
>> Hi John -
>> Thanks for posting the ADF snippet!
>> Unless you live along the 0 degree line that more or less crosses
>> Greenwich, England, I don't think the vacuumer is running when you
>> think it should.
>> SQLNS keeps time in UTC, formerly known as GMT. To get local time from
>> UTC time, you need to add or substract a number of hours (depending on
>> the time zone) to/from the UTC. For example, the Central Standard Time
>> has a -6 hour offset from UTC. So if you live in say Chicago, you're
>> actually running the vacuumer at 300pm (2100 - 600 = 1500).
>> Could that be your issue?
>> BTW - here's a link to a site that talks about UTC and the offsets.
>> Joe Webb
>> SQL Server MVP
>> Get up to speed quickly with SQLNS
>> I support PASS, the Professional Association for SQL Server.
>> On Thu, 15 Sep 2005 06:00:08 -0700, "J" <[email protected]>
>> >Hi Joe,
>> >Answers to your questions :-
>> >1. Yup, here's the section from the config file:
>> > <Vacuum>
>> > <RetentionAge>P1DT00H00M00S</RetentionAge>
>> > <VacuumSchedule>
>> > <Schedule>
>> > <StartTime>21:00:00</StartTime>
>> > <Duration>P0DT03H00M00S</Duration>
>> > </Schedule>
>> > </VacuumSchedule>
>> > </Vacuum>
>> >2. Yup :)
>> >3. v2.0
>> >4. I'll have to let you know that one tomorrow... I just checked, and the
>> >State returned the time from todays manual run, and the Schedule said:
>> >2, 01/01/1900, 21:00:00, 10800