Maintenance Plan Changes in SQL Server 2005 SP2

Users of SQL Server 2005 maintenance plans should be aware of a change in
SP2 that affects existing cleanup tasks until updated using SQL Server SP2
tools.
Who is affected?
You are affected if you use SQL Server 2005 maintenance plans, those plans
include a History Cleanup Task or a Maintenance Cleanup Task, and you
install SQL Server 2005 SP2. Users of SQL Server 2000 legacy maintenance
plans are not affected.
What is the issue?
Some maintenance plans might include the Maintenance Cleanup Task and the
History Cleanup Task, which allow users to delete information older than a
specified interval. When SQL Server 2005 was released, this interval was
measured in days, weeks, months, or years. In response to customer feedback,
SQL Server 2005 SP2 includes significant enhancements to maintenance plans,
including an enhancement that allows users to specify the cleanup interval
in hours. After upgrading to SP2, and until you update cleanup tasks using
SQL Server SP2 tools as described below, existing cleanup task intervals are
misinterpreted. This leads to earlier data cleanup than was intended.
What if I have already installed SP2 on my server?
You can restore your maintenance plans to their former behavior by opening
them up in the Maintenance Plan Designer, opening any cleanup tasks,
adjusting the age units to the proper value, and saving the maintenance
plan. Use SQL Server 2005 SP2 tools to make these changes.
What if I haven't yet installed SP2 on my server?
We are currently investigating our approach to this problem and will provide
guidance shortly. If you depend on the Maintenance Cleanup Task or the
History Cleanup Task and are not able to verify and possibly update cleanup
tasks using matching server and tool versions, you may want to wait for that
guidance before installing SP2.
Wow, how many dba's will loose their jobs over that one? How did something
like that get past QA or even the developers of that feature?
Andrew J. Kelly SQL MVP
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:uzdQ8B$VHHA.488@.TK2MSFTNGP06.phx.gbl...
> Users of SQL Server 2005 maintenance plans should be aware of a change in
> SP2 that affects existing cleanup tasks until updated using SQL Server SP2
> tools.
> Who is affected?
> You are affected if you use SQL Server 2005 maintenance plans, those plans
> include a History Cleanup Task or a Maintenance Cleanup Task, and you
> install SQL Server 2005 SP2. Users of SQL Server 2000 legacy maintenance
> plans are not affected.
> What is the issue?
> Some maintenance plans might include the Maintenance Cleanup Task and the
> History Cleanup Task, which allow users to delete information older than a
> specified interval. When SQL Server 2005 was released, this interval was
> measured in days, weeks, months, or years. In response to customer
> feedback, SQL Server 2005 SP2 includes significant enhancements to
> maintenance plans, including an enhancement that allows users to specify
> the cleanup interval in hours. After upgrading to SP2, and until you
> update cleanup tasks using SQL Server SP2 tools as described below,
> existing cleanup task intervals are misinterpreted. This leads to earlier
> data cleanup than was intended.
> What if I have already installed SP2 on my server?
> You can restore your maintenance plans to their former behavior by opening
> them up in the Maintenance Plan Designer, opening any cleanup tasks,
> adjusting the age units to the proper value, and saving the maintenance
> plan. Use SQL Server 2005 SP2 tools to make these changes.
> What if I haven't yet installed SP2 on my server?
> We are currently investigating our approach to this problem and will
> provide guidance shortly. If you depend on the Maintenance Cleanup Task or
> the History Cleanup Task and are not able to verify and possibly update
> cleanup tasks using matching server and tool versions, you may want to
> wait for that guidance before installing SP2.
>
|||Ed,
Pre SP2 the maintenance plans created SSIS packages. Is this still the
behaviour in SP2?
Thanks
Chris
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:uzdQ8B$VHHA.488@.TK2MSFTNGP06.phx.gbl...
> Users of SQL Server 2005 maintenance plans should be aware of a change in
> SP2 that affects existing cleanup tasks until updated using SQL Server SP2
> tools.
> Who is affected?
> You are affected if you use SQL Server 2005 maintenance plans, those plans
> include a History Cleanup Task or a Maintenance Cleanup Task, and you
> install SQL Server 2005 SP2. Users of SQL Server 2000 legacy maintenance
> plans are not affected.
> What is the issue?
> Some maintenance plans might include the Maintenance Cleanup Task and the
> History Cleanup Task, which allow users to delete information older than a
> specified interval. When SQL Server 2005 was released, this interval was
> measured in days, weeks, months, or years. In response to customer
> feedback, SQL Server 2005 SP2 includes significant enhancements to
> maintenance plans, including an enhancement that allows users to specify
> the cleanup interval in hours. After upgrading to SP2, and until you
> update cleanup tasks using SQL Server SP2 tools as described below,
> existing cleanup task intervals are misinterpreted. This leads to earlier
> data cleanup than was intended.
> What if I have already installed SP2 on my server?
> You can restore your maintenance plans to their former behavior by opening
> them up in the Maintenance Plan Designer, opening any cleanup tasks,
> adjusting the age units to the proper value, and saving the maintenance
> plan. Use SQL Server 2005 SP2 tools to make these changes.
> What if I haven't yet installed SP2 on my server?
> We are currently investigating our approach to this problem and will
> provide guidance shortly. If you depend on the Maintenance Cleanup Task or
> the History Cleanup Task and are not able to verify and possibly update
> cleanup tasks using matching server and tool versions, you may want to
> wait for that guidance before installing SP2.
>