Showing posts with label sp2. Show all posts
Showing posts with label sp2. Show all posts

Wednesday, March 28, 2012

Maintenance Plan Error

Windows 20003 Enterprise server

SQL 2005 Standard with SP2

When I try and create a maintenance plan either via the wizard or just create new, I get the following error. Can anyone help please. thanks

===================================

Cannot show requested dialog.

===================================

Unable to execute requested command.


Program Location:

at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItem.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc)
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()

===================================

Method not found: 'Void Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'. (Microsoft.SqlServer.Management.MaintenancePlanWizard)


Program Location:

at Microsoft.SqlServer.Management.MaintenancePlanWizard.MaintenancePlanWizardForm..ctor(XmlDocument doc, IServiceProvider serviceProvider)

Hello Theon,

This sounds like your client tools are older than SP2. The SP2 version of the Microsoft.SqlServer.MaintenancePlanTasks.dll assembly removed the function mentioned in the error message, so that's why the function cannot be found.. Can you check what version of Management Studio you're running, and see if its older than SP2? Also are you running Management Studio on the sql server machine, or connecting to it remotely?

James

|||

Here is the version

Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

I am connecting on the server

|||Applied sp2 and all is well thanks
|||

Glad to help, Theon.

James

Maintenance Plan does not show up under Management Folder

Hi.
I am running SQL 2005 SP2 and when I connect through Visual Studio I do not
see the maintenance plan option under Management. I have tried connecting
with the SA account and my AD account and neither one has this option. They
are both assigned the role of sysadmin. Any thoughts?
Thanks
AlAre you connecting to Express Edition? Does the Maintenance Plans folder
show up when connecting through Management Studio?
Aaron Bertrand
SQL Server MVP
"Al Stephenson" <AlStephenson@.discussions.microsoft.com> wrote in message
news:0130F16D-725C-47B4-8E86-EED40B8D45A0@.microsoft.com...
> Hi.
> I am running SQL 2005 SP2 and when I connect through Visual Studio I do
> not
> see the maintenance plan option under Management. I have tried connecting
> with the SA account and my AD account and neither one has this option.
> They
> are both assigned the role of sysadmin. Any thoughts?
> Thanks
> Al|||Looks like instead of SQL 2005 Standard we are running SQL 2005 Express. Thi
s
is part of a Sharepoint install. Will Express support maintenance plans? It
does not show up under Management Studio.
Thanks
"Aaron Bertrand [SQL Server MVP]" wrote:

> Are you connecting to Express Edition? Does the Maintenance Plans folder
> show up when connecting through Management Studio?
> --
> Aaron Bertrand
> SQL Server MVP
>
> "Al Stephenson" <AlStephenson@.discussions.microsoft.com> wrote in message
> news:0130F16D-725C-47B4-8E86-EED40B8D45A0@.microsoft.com...
>
>|||> Looks like instead of SQL 2005 Standard we are running SQL 2005 Express.
> This
> is part of a Sharepoint install. Will Express support maintenance plans?
> It
> does not show up under Management Studio.
No, and if the node is there in Management Studio Express Edition, it is
likely only there to manage other instances... since Express does not have
Agent, which is a requirement for maintenance plans.
Andrew Kelly recently pointed out some links to help you achieve the same
kind of functionality through other means:
Backing up Express
http://blogs.msdn.com/rogerwolterbl.../13/575974.aspx
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=29
Automating Database maintenance in SQL 2005 Express Edition Part II
Aaron Bertrand
SQL Server MVP|||Thanks for the info. I do have one other instance of SQL 2005 Standard
edition running and I connected to it with Management Studio and I see the
Maintenance Plan folder but when I right click on it the only option is to
refresh. I have sysadmin role assigned to my AD account and SQL is configure
d
for SQL and Windows Authentication. What am I missing?
"Aaron Bertrand [SQL Server MVP]" wrote:

> No, and if the node is there in Management Studio Express Edition, it is
> likely only there to manage other instances... since Express does not have
> Agent, which is a requirement for maintenance plans.
> Andrew Kelly recently pointed out some links to help you achieve the same
> kind of functionality through other means:
> Backing up Express
> http://blogs.msdn.com/rogerwolterbl.../13/575974.aspx
> http://www.sqldbatips.com/showarticle.asp?ID=27
> Automating Database maintenance in SQL 2005 Express Edition Part I
> http://www.sqldbatips.com/showarticle.asp?ID=29
> Automating Database maintenance in SQL 2005 Express Edition Part II
> --
> Aaron Bertrand
> SQL Server MVP
>
>|||Are you using Management Studio Express Edition, or Management Studio?
Aaron Bertrand
SQL Server MVP
"Al Stephenson" <AlStephenson@.discussions.microsoft.com> wrote in message
news:64F1F0C8-8A53-4299-9D7F-C165F90BB515@.microsoft.com...[vbcol=seagreen]
> Thanks for the info. I do have one other instance of SQL 2005 Standard
> edition running and I connected to it with Management Studio and I see the
> Maintenance Plan folder but when I right click on it the only option is to
> refresh. I have sysadmin role assigned to my AD account and SQL is
> configured
> for SQL and Windows Authentication. What am I missing?
> "Aaron Bertrand [SQL Server MVP]" wrote:
>sql

Maintenance Plan does not show up under Management Folder

Hi.
I am running SQL 2005 SP2 and when I connect through Visual Studio I do not
see the maintenance plan option under Management. I have tried connecting
with the SA account and my AD account and neither one has this option. They
are both assigned the role of sysadmin. Any thoughts?
Thanks
Al
Are you connecting to Express Edition? Does the Maintenance Plans folder
show up when connecting through Management Studio?
Aaron Bertrand
SQL Server MVP
"Al Stephenson" <AlStephenson@.discussions.microsoft.com> wrote in message
news:0130F16D-725C-47B4-8E86-EED40B8D45A0@.microsoft.com...
> Hi.
> I am running SQL 2005 SP2 and when I connect through Visual Studio I do
> not
> see the maintenance plan option under Management. I have tried connecting
> with the SA account and my AD account and neither one has this option.
> They
> are both assigned the role of sysadmin. Any thoughts?
> Thanks
> Al
|||Looks like instead of SQL 2005 Standard we are running SQL 2005 Express. This
is part of a Sharepoint install. Will Express support maintenance plans? It
does not show up under Management Studio.
Thanks
"Aaron Bertrand [SQL Server MVP]" wrote:

> Are you connecting to Express Edition? Does the Maintenance Plans folder
> show up when connecting through Management Studio?
> --
> Aaron Bertrand
> SQL Server MVP
>
> "Al Stephenson" <AlStephenson@.discussions.microsoft.com> wrote in message
> news:0130F16D-725C-47B4-8E86-EED40B8D45A0@.microsoft.com...
>
>
|||> Looks like instead of SQL 2005 Standard we are running SQL 2005 Express.
> This
> is part of a Sharepoint install. Will Express support maintenance plans?
> It
> does not show up under Management Studio.
No, and if the node is there in Management Studio Express Edition, it is
likely only there to manage other instances... since Express does not have
Agent, which is a requirement for maintenance plans.
Andrew Kelly recently pointed out some links to help you achieve the same
kind of functionality through other means:
Backing up Express
http://blogs.msdn.com/rogerwolterblog/archive/2006/04/13/575974.aspx
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=29
Automating Database maintenance in SQL 2005 Express Edition Part II
Aaron Bertrand
SQL Server MVP
|||Thanks for the info. I do have one other instance of SQL 2005 Standard
edition running and I connected to it with Management Studio and I see the
Maintenance Plan folder but when I right click on it the only option is to
refresh. I have sysadmin role assigned to my AD account and SQL is configured
for SQL and Windows Authentication. What am I missing?
"Aaron Bertrand [SQL Server MVP]" wrote:

> No, and if the node is there in Management Studio Express Edition, it is
> likely only there to manage other instances... since Express does not have
> Agent, which is a requirement for maintenance plans.
> Andrew Kelly recently pointed out some links to help you achieve the same
> kind of functionality through other means:
> Backing up Express
> http://blogs.msdn.com/rogerwolterblog/archive/2006/04/13/575974.aspx
> http://www.sqldbatips.com/showarticle.asp?ID=27
> Automating Database maintenance in SQL 2005 Express Edition Part I
> http://www.sqldbatips.com/showarticle.asp?ID=29
> Automating Database maintenance in SQL 2005 Express Edition Part II
> --
> Aaron Bertrand
> SQL Server MVP
>
>
|||Are you using Management Studio Express Edition, or Management Studio?
Aaron Bertrand
SQL Server MVP
"Al Stephenson" <AlStephenson@.discussions.microsoft.com> wrote in message
news:64F1F0C8-8A53-4299-9D7F-C165F90BB515@.microsoft.com...[vbcol=seagreen]
> Thanks for the info. I do have one other instance of SQL 2005 Standard
> edition running and I connected to it with Management Studio and I see the
> Maintenance Plan folder but when I right click on it the only option is to
> refresh. I have sysadmin role assigned to my AD account and SQL is
> configured
> for SQL and Windows Authentication. What am I missing?
> "Aaron Bertrand [SQL Server MVP]" wrote:

Maintenance Plan does not show up under Management Folder

Hi.
I am running SQL 2005 SP2 and when I connect through Visual Studio I do not
see the maintenance plan option under Management. I have tried connecting
with the SA account and my AD account and neither one has this option. They
are both assigned the role of sysadmin. Any thoughts?
Thanks
AlAre you connecting to Express Edition? Does the Maintenance Plans folder
show up when connecting through Management Studio?
--
Aaron Bertrand
SQL Server MVP
"Al Stephenson" <AlStephenson@.discussions.microsoft.com> wrote in message
news:0130F16D-725C-47B4-8E86-EED40B8D45A0@.microsoft.com...
> Hi.
> I am running SQL 2005 SP2 and when I connect through Visual Studio I do
> not
> see the maintenance plan option under Management. I have tried connecting
> with the SA account and my AD account and neither one has this option.
> They
> are both assigned the role of sysadmin. Any thoughts?
> Thanks
> Al|||Looks like instead of SQL 2005 Standard we are running SQL 2005 Express. This
is part of a Sharepoint install. Will Express support maintenance plans? It
does not show up under Management Studio.
Thanks
"Aaron Bertrand [SQL Server MVP]" wrote:
> Are you connecting to Express Edition? Does the Maintenance Plans folder
> show up when connecting through Management Studio?
> --
> Aaron Bertrand
> SQL Server MVP
>
> "Al Stephenson" <AlStephenson@.discussions.microsoft.com> wrote in message
> news:0130F16D-725C-47B4-8E86-EED40B8D45A0@.microsoft.com...
> > Hi.
> >
> > I am running SQL 2005 SP2 and when I connect through Visual Studio I do
> > not
> > see the maintenance plan option under Management. I have tried connecting
> > with the SA account and my AD account and neither one has this option.
> > They
> > are both assigned the role of sysadmin. Any thoughts?
> >
> > Thanks
> >
> > Al
>
>|||> Looks like instead of SQL 2005 Standard we are running SQL 2005 Express.
> This
> is part of a Sharepoint install. Will Express support maintenance plans?
> It
> does not show up under Management Studio.
No, and if the node is there in Management Studio Express Edition, it is
likely only there to manage other instances... since Express does not have
Agent, which is a requirement for maintenance plans.
Andrew Kelly recently pointed out some links to help you achieve the same
kind of functionality through other means:
Backing up Express
http://blogs.msdn.com/rogerwolterblog/archive/2006/04/13/575974.aspx
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=29
Automating Database maintenance in SQL 2005 Express Edition Part II
--
Aaron Bertrand
SQL Server MVP|||Thanks for the info. I do have one other instance of SQL 2005 Standard
edition running and I connected to it with Management Studio and I see the
Maintenance Plan folder but when I right click on it the only option is to
refresh. I have sysadmin role assigned to my AD account and SQL is configured
for SQL and Windows Authentication. What am I missing?
"Aaron Bertrand [SQL Server MVP]" wrote:
> > Looks like instead of SQL 2005 Standard we are running SQL 2005 Express.
> > This
> > is part of a Sharepoint install. Will Express support maintenance plans?
> > It
> > does not show up under Management Studio.
> No, and if the node is there in Management Studio Express Edition, it is
> likely only there to manage other instances... since Express does not have
> Agent, which is a requirement for maintenance plans.
> Andrew Kelly recently pointed out some links to help you achieve the same
> kind of functionality through other means:
> Backing up Express
> http://blogs.msdn.com/rogerwolterblog/archive/2006/04/13/575974.aspx
> http://www.sqldbatips.com/showarticle.asp?ID=27
> Automating Database maintenance in SQL 2005 Express Edition Part I
> http://www.sqldbatips.com/showarticle.asp?ID=29
> Automating Database maintenance in SQL 2005 Express Edition Part II
> --
> Aaron Bertrand
> SQL Server MVP
>
>|||Are you using Management Studio Express Edition, or Management Studio?
--
Aaron Bertrand
SQL Server MVP
"Al Stephenson" <AlStephenson@.discussions.microsoft.com> wrote in message
news:64F1F0C8-8A53-4299-9D7F-C165F90BB515@.microsoft.com...
> Thanks for the info. I do have one other instance of SQL 2005 Standard
> edition running and I connected to it with Management Studio and I see the
> Maintenance Plan folder but when I right click on it the only option is to
> refresh. I have sysadmin role assigned to my AD account and SQL is
> configured
> for SQL and Windows Authentication. What am I missing?
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> > Looks like instead of SQL 2005 Standard we are running SQL 2005
>> > Express.
>> > This
>> > is part of a Sharepoint install. Will Express support maintenance
>> > plans?
>> > It
>> > does not show up under Management Studio.
>> No, and if the node is there in Management Studio Express Edition, it is
>> likely only there to manage other instances... since Express does not
>> have
>> Agent, which is a requirement for maintenance plans.
>> Andrew Kelly recently pointed out some links to help you achieve the same
>> kind of functionality through other means:
>> Backing up Express
>> http://blogs.msdn.com/rogerwolterblog/archive/2006/04/13/575974.aspx
>> http://www.sqldbatips.com/showarticle.asp?ID=27
>> Automating Database maintenance in SQL 2005 Express Edition Part I
>> http://www.sqldbatips.com/showarticle.asp?ID=29
>> Automating Database maintenance in SQL 2005 Express Edition Part II
>> --
>> Aaron Bertrand
>> SQL Server MVP
>>

maintenance plan Cleanup Task

Hello all,

What is the latest after SP2 on the Maintenace Cleanup Task?

Has anyone been able to successfully delete old backup files(*.bak) and tran logs (*.trn) TOGETHER using maintenance plan cleanup task in SQL 2005 SP2 with all the htfixes instaled? .

In other words can EXECUTE master.dbo.xp_delete_file 0,N'D:\backups',N'bak',N'2007-07-12T10:12:03',1 be used with bak and trn at the same time

Thanks in advanced

This has been fixed in the latest cumulative update for SQL Server. Contact Customer Support and they will direct you to the fix.

jkh

maintenance plan Cleanup Task

Hello all,

What is the latest after SP2 on the Maintenace Cleanup Task?

Has anyone been able to successfully delete old backup files(*.bak) and tran logs (*.trn) TOGETHER using maintenance plan cleanup task in SQL 2005 SP2 with all the htfixes instaled? .

In other words can EXECUTE master.dbo.xp_delete_file 0,N'D:\backups',N'bak',N'2007-07-12T10:12:03',1 be used with bak and trn at the same time

Thanks in advanced

This has been fixed in the latest cumulative update for SQL Server. Contact Customer Support and they will direct you to the fix.

jkh

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.

I installed sp2 on my server. It failed on database engine service. And my maintance plans corrupted. I am not able to open existing plan or create new plan.

Gives the following error:

Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSContainer90'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{8BDFE892-E9D8-4D23-9739-DA807BCDC2AC}' failed due to the following error: Interface not registered (Exception from HRESULT: 0x80040155). (Microsoft.SqlServer.ManagedDTS)

Any help?

|||Good to see cleanup task in maintenance plan. But the task can only delete one type of files. If I want to delete db backup files, log backup files and plan log files, I need to add two more cleanup tasks after creating plan. Why can't add cleanup option in backup and logging page like sql2k's plan does?|||I have the same error. Does anybody out there have an answer to this? Please email me a bkellman@.hcfmw.com|||There is new post sp2 fix, check kb934458.|||

the update to SP2 did not fix it for me.

however this solution in a different blog did: regsvr32 “C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll”

|||

Rmiao,

You don't need to create new tasks to perform the cleanup that you want. You can define one type of clean up task in a miantenance plan and then add addtional steps to the plan to clean up other types of files as well. The Wizard does not deal with this very well, expecially since you want to remove several diferent types of files.

Once you have created the Maintenance Plan that you desire, edit the maintenance plan. With this method the plan will appear as a flow chart with all of the steps shows as nodes connected by conditional lines. You are free to add as many addtional tasks as you wish at this point. I further suggest that conditions be added so that previous backup files are not deleted in case a new one is not created for some reason (i.e. full disk drive, missing/bad media, etc.)

|||Jeff, that's what I did. But why can't Microsoft look at sql2k's maintenance plan when design sql2k5's?|||The patch that fixes the maintenance plan bug is supposedly

SQLServer2005-KB933508-x86-ENU.exe, which addresses KB933508. Unfortunately the installer seems to be buggy. When I try to install the patch, I get to a point where I cannot select anything to install from the tree, and the Next button is grey (disabled).

Anyone experience this, or know of another patch that includes this fix that actually installs?

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.

I installed sp2 on my server. It failed on database engine service. And my maintance plans corrupted. I am not able to open existing plan or create new plan.

Gives the following error:

Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSContainer90'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{8BDFE892-E9D8-4D23-9739-DA807BCDC2AC}' failed due to the following error: Interface not registered (Exception from HRESULT: 0x80040155). (Microsoft.SqlServer.ManagedDTS)

Any help?

|||Good to see cleanup task in maintenance plan. But the task can only delete one type of files. If I want to delete db backup files, log backup files and plan log files, I need to add two more cleanup tasks after creating plan. Why can't add cleanup option in backup and logging page like sql2k's plan does?|||I have the same error. Does anybody out there have an answer to this? Please email me a bkellman@.hcfmw.com|||There is new post sp2 fix, check kb934458.|||

the update to SP2 did not fix it for me.

however this solution in a different blog did: regsvr32 “C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll”

|||

Rmiao,

You don't need to create new tasks to perform the cleanup that you want. You can define one type of clean up task in a miantenance plan and then add addtional steps to the plan to clean up other types of files as well. The Wizard does not deal with this very well, expecially since you want to remove several diferent types of files.

Once you have created the Maintenance Plan that you desire, edit the maintenance plan. With this method the plan will appear as a flow chart with all of the steps shows as nodes connected by conditional lines. You are free to add as many addtional tasks as you wish at this point. I further suggest that conditions be added so that previous backup files are not deleted in case a new one is not created for some reason (i.e. full disk drive, missing/bad media, etc.)

|||Jeff, that's what I did. But why can't Microsoft look at sql2k's maintenance plan when design sql2k5's?|||The patch that fixes the maintenance plan bug is supposedly

SQLServer2005-KB933508-x86-ENU.exe, which addresses KB933508. Unfortunately the installer seems to be buggy. When I try to install the patch, I get to a point where I cannot select anything to install from the tree, and the Next button is grey (disabled).

Anyone experience this, or know of another patch that includes this fix that actually installs?

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.
>sql

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.

I installed sp2 on my server. It failed on database engine service. And my maintance plans corrupted. I am not able to open existing plan or create new plan.

Gives the following error:

Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSContainer90'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{8BDFE892-E9D8-4D23-9739-DA807BCDC2AC}' failed due to the following error: Interface not registered (Exception from HRESULT: 0x80040155). (Microsoft.SqlServer.ManagedDTS)

Any help?

|||Good to see cleanup task in maintenance plan. But the task can only delete one type of files. If I want to delete db backup files, log backup files and plan log files, I need to add two more cleanup tasks after creating plan. Why can't add cleanup option in backup and logging page like sql2k's plan does?|||I have the same error. Does anybody out there have an answer to this? Please email me a bkellman@.hcfmw.com|||There is new post sp2 fix, check kb934458.|||

the update to SP2 did not fix it for me.

however this solution in a different blog did: regsvr32 “C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll”

|||

Rmiao,

You don't need to create new tasks to perform the cleanup that you want. You can define one type of clean up task in a miantenance plan and then add addtional steps to the plan to clean up other types of files as well. The Wizard does not deal with this very well, expecially since you want to remove several diferent types of files.

Once you have created the Maintenance Plan that you desire, edit the maintenance plan. With this method the plan will appear as a flow chart with all of the steps shows as nodes connected by conditional lines. You are free to add as many addtional tasks as you wish at this point. I further suggest that conditions be added so that previous backup files are not deleted in case a new one is not created for some reason (i.e. full disk drive, missing/bad media, etc.)

|||Jeff, that's what I did. But why can't Microsoft look at sql2k's maintenance plan when design sql2k5's?|||The patch that fixes the maintenance plan bug is supposedly

SQLServer2005-KB933508-x86-ENU.exe, which addresses KB933508. Unfortunately the installer seems to be buggy. When I try to install the patch, I get to a point where I cannot select anything to install from the tree, and the Next button is grey (disabled).

Anyone experience this, or know of another patch that includes this fix that actually installs?

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.

I installed sp2 on my server. It failed on database engine service. And my maintance plans corrupted. I am not able to open existing plan or create new plan.

Gives the following error:

Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSContainer90'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{8BDFE892-E9D8-4D23-9739-DA807BCDC2AC}' failed due to the following error: Interface not registered (Exception from HRESULT: 0x80040155). (Microsoft.SqlServer.ManagedDTS)

Any help?

|||Good to see cleanup task in maintenance plan. But the task can only delete one type of files. If I want to delete db backup files, log backup files and plan log files, I need to add two more cleanup tasks after creating plan. Why can't add cleanup option in backup and logging page like sql2k's plan does?|||I have the same error. Does anybody out there have an answer to this? Please email me a bkellman@.hcfmw.com|||There is new post sp2 fix, check kb934458.|||

the update to SP2 did not fix it for me.

however this solution in a different blog did: regsvr32 “C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll”

|||

Rmiao,

You don't need to create new tasks to perform the cleanup that you want. You can define one type of clean up task in a miantenance plan and then add addtional steps to the plan to clean up other types of files as well. The Wizard does not deal with this very well, expecially since you want to remove several diferent types of files.

Once you have created the Maintenance Plan that you desire, edit the maintenance plan. With this method the plan will appear as a flow chart with all of the steps shows as nodes connected by conditional lines. You are free to add as many addtional tasks as you wish at this point. I further suggest that conditions be added so that previous backup files are not deleted in case a new one is not created for some reason (i.e. full disk drive, missing/bad media, etc.)

|||Jeff, that's what I did. But why can't Microsoft look at sql2k's maintenance plan when design sql2k5's?|||The patch that fixes the maintenance plan bug is supposedly

SQLServer2005-KB933508-x86-ENU.exe, which addresses KB933508. Unfortunately the installer seems to be buggy. When I try to install the patch, I get to a point where I cannot select anything to install from the tree, and the Next button is grey (disabled).

Anyone experience this, or know of another patch that includes this fix that actually installs?

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.

Users, also please make a note of README for SP2:

The following error message is returned if you use a tool from a previous version to open an SP2 maintenance plan created with the maintenance plan designer:

"This maintenance plan has been modified using a tool other than the maintenance plan designer. You must use SQL Server Integration Services to modify this maintenance plan from now on."

To resolve this issue, we recommend that you upgrade your tools to SQL Server 2005 SP2. We also recommend using the maintenance plan designer to modify the plan, rather than Integration Services as mentioned in the error message.

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.

Users, also please make a note of README for SP2:

The following error message is returned if you use a tool from a previous version to open an SP2 maintenance plan created with the maintenance plan designer:

"This maintenance plan has been modified using a tool other than the maintenance plan designer. You must use SQL Server Integration Services to modify this maintenance plan from now on."

To resolve this issue, we recommend that you upgrade your tools to SQL Server 2005 SP2. We also recommend using the maintenance plan designer to modify the plan, rather than Integration Services as mentioned in the error message.

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.
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:uKlNt%23%23VHHA.4668@.TK2MSFTNGP04.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.
>
|||Chris Wood (anonymous@.discussions.microsoft.com) writes:
> Pre SP2 the maintenance plans created SSIS packages. Is this still the
> behaviour in SP2?
I'm not into maintenance plans myself, but I believe that in SP2,
maintenance plans are part of the engine, and SSIS is not required.
There is a discussion on this in "What's New in SP2" in Books Online.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||Yes, SP2 Maintenance Plans still create SSIS packages. We do not plan on
changing this in the near future.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%232F$oTeWHHA.1016@.TK2MSFTNGP04.phx.gbl...
> 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:uKlNt%23%23VHHA.4668@.TK2MSFTNGP04.phx.gbl...
>
|||Hello,
I used method:
public void AddAgentJob(ServerConnection LocalConnObj, string proxyName)
(class
Microsoft.SqlServer.Management.DatabaseMaintenance .MaintenancePlanSubPlan)
but after installing SP2 for MS SQL Server, I can't find it.
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:uKlNt%23%23VHHA.4668@.TK2MSFTNGP04.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.
>
sql

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.
>

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.
>

Friday, March 23, 2012

maintenance plan

We have two SQL 2000 servers, one runs on SP2 and another
one runs on SP3, I set up the same maintanence plans on
them and selected 'attemp to repair any minor problems'
but the job 'Integrity Check' failed at 'Check data and
index linkage' due to 'database needs to be in single user
mode' on both user and system databases. Any idea what I
did wrong? OS is Win2K SP3.
Many thanks!You didn't do anything wrong, it needs to be in single user mode to do this
and if there is any connection in the db it can't put it in single user
mode. You should uncheck this anyway. Let it report the errors and then
you decide how and when to fix them.
--
Andrew J. Kelly
SQL Server MVP
"Ray Yan" <remonyan@.hotmail.com> wrote in message
news:61d901c34107$597b1180$7d02280a@.phx.gbl...
> We have two SQL 2000 servers, one runs on SP2 and another
> one runs on SP3, I set up the same maintanence plans on
> them and selected 'attemp to repair any minor problems'
> but the job 'Integrity Check' failed at 'Check data and
> index linkage' due to 'database needs to be in single user
> mode' on both user and system databases. Any idea what I
> did wrong? OS is Win2K SP3.
> Many thanks!

Maintenance Plan

I am running SQL 2005 SP2
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
When I try to create a maintenance plan it says
TITLE: Microsoft SQL Server Management Studio
--
Method not found: 'Void
Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'.
(Microsoft.SqlServer.MaintenancePlanTasksUI)
--
BUTTONS:
OK
--
A search on the web didn't turn much up. One posting said there was a new
version of SP2 but I haven't found a newer one.
Any Ideas?
Thankssuper1,
I don't have this problem and I am currently at build 9.00.3159. If you go
to http://technet.microsoft.com/en-us/default.aspx and search "SQL Server
2005 SP2" "Critical Update" you will find some information on post-SP2
patches. (From reading this, perhaps I need to apply at least one more.)
RLF
"super1" <superbrownbrown1@.nospam.nospam> wrote in message
news:%234VBEHC4HHA.3400@.TK2MSFTNGP03.phx.gbl...
>I am running SQL 2005 SP2
> Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
> Feb 9 2007 22:47:07
> Copyright (c) 1988-2005 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> When I try to create a maintenance plan it says
> TITLE: Microsoft SQL Server Management Studio
> --
> Method not found: 'Void
> Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'.
> (Microsoft.SqlServer.MaintenancePlanTasksUI)
> --
> BUTTONS:
> OK
> --
>
> A search on the web didn't turn much up. One posting said there was a new
> version of SP2 but I haven't found a newer one.
> Any Ideas?
> Thanks|||You need to apply a hotfix or the cumulative update:
http://support.microsoft.com/kb/933508
http://support.microsoft.com/kb/936305
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"super1" <superbrownbrown1@.nospam.nospam> wrote in message
news:%234VBEHC4HHA.3400@.TK2MSFTNGP03.phx.gbl...
>I am running SQL 2005 SP2
> Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
> Feb 9 2007 22:47:07
> Copyright (c) 1988-2005 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> When I try to create a maintenance plan it says
> TITLE: Microsoft SQL Server Management Studio
> --
> Method not found: 'Void
> Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'.
> (Microsoft.SqlServer.MaintenancePlanTasksUI)
> --
> BUTTONS:
> OK
> --
>
> A search on the web didn't turn much up. One posting said there was a new
> version of SP2 but I haven't found a newer one.
> Any Ideas?
> Thanks|||Thanks for the info. I have requested the patch.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%236oJBmC4HHA.2312@.TK2MSFTNGP06.phx.gbl...
> You need to apply a hotfix or the cumulative update:
> http://support.microsoft.com/kb/933508
> http://support.microsoft.com/kb/936305
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "super1" <superbrownbrown1@.nospam.nospam> wrote in message
> news:%234VBEHC4HHA.3400@.TK2MSFTNGP03.phx.gbl...
>>I am running SQL 2005 SP2
>> Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
>> Feb 9 2007 22:47:07
>> Copyright (c) 1988-2005 Microsoft Corporation
>> Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
>> When I try to create a maintenance plan it says
>> TITLE: Microsoft SQL Server Management Studio
>> --
>> Method not found: 'Void
>> Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'.
>> (Microsoft.SqlServer.MaintenancePlanTasksUI)
>> --
>> BUTTONS:
>> OK
>> --
>>
>> A search on the web didn't turn much up. One posting said there was a
>> new version of SP2 but I haven't found a newer one.
>> Any Ideas?
>> Thanks
>|||Hi superbrown,
Did this issue persist after you installed the patch?
Normally this issue should not occur if SQL Server 2005 SP2 was
successfully installed. If this issue persists, I recommend that you check
if your SQL Server 2005 SP2 had been installed successfully. You can check
the setup logs (summary.txt etc) from this folder %ProgramFiles%\Microsoft
SQL Server\90\Setup Bootstrap\LOG\Hotfix.
If there is no error in the setup log, as a possible workaround, I
recommend that just uninstall SQL Server 2005 Client Tools, and then
reinstall it and SQL Server 2005 SP2 to see if this issue persists. To
uninstall SQL Server 2005 Client Tools, you can refer to the following
steps:
1. Open Control Panel -> Add or Remove Programs
2. Select Microsoft SQL Server 2005 from the list, click Remove, just
select Workstation Components from the "Remove SQL Server 2005 common
components" list, and click Next.
3. Follow the wizard to end the uninstallation.
Hope this helps. If this issue persists, I recommend that send the SP2
setup logs to me for further research. However the process may need your
sending me (changliw_at_microsoft_dot_com) an email response so that I can
create a workspace for your uploading the files.
If you have any other questions or concerns, please feel free to let me
know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||I applied this hotfix pack.
http://support.microsoft.com/kb/936305
And it didn't fix the problem. The log has an entry that says
Product : SQL Server Tools and Workstation Components 2005
Product Version (Previous): 1399
Product Version (Final) :
Status : NA
Log File :
Error Description : The product instance SQL Tools does not have
prerequisite update 3042 installed. Update 3175 is dependent on prerequisite
update 3042. Exit setup and refer to the Knowledge Base article to find the
prerequisite patch. Install the prerequisite and rerun the installation.
So I need another hotfix first?
This other hotfix was referenced by Andrew.
http://support.microsoft.com/kb/933508
I have requested it from Microsoft but they have not sent it to me yet.
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:gDPvcGJ4HHA.4100@.TK2MSFTNGHUB02.phx.gbl...
> Hi superbrown,
> Did this issue persist after you installed the patch?
> Normally this issue should not occur if SQL Server 2005 SP2 was
> successfully installed. If this issue persists, I recommend that you check
> if your SQL Server 2005 SP2 had been installed successfully. You can check
> the setup logs (summary.txt etc) from this folder %ProgramFiles%\Microsoft
> SQL Server\90\Setup Bootstrap\LOG\Hotfix.
> If there is no error in the setup log, as a possible workaround, I
> recommend that just uninstall SQL Server 2005 Client Tools, and then
> reinstall it and SQL Server 2005 SP2 to see if this issue persists. To
> uninstall SQL Server 2005 Client Tools, you can refer to the following
> steps:
> 1. Open Control Panel -> Add or Remove Programs
> 2. Select Microsoft SQL Server 2005 from the list, click Remove, just
> select Workstation Components from the "Remove SQL Server 2005 common
> components" list, and click Next.
> 3. Follow the wizard to end the uninstallation.
> Hope this helps. If this issue persists, I recommend that send the SP2
> setup logs to me for further research. However the process may need your
> sending me (changliw_at_microsoft_dot_com) an email response so that I can
> create a workspace for your uploading the files.
> If you have any other questions or concerns, please feel free to let me
> know. It is my pleasure to be of assistance.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ======================================================>|||I removed the management tools, re-applied SP2 and added the tools back in.
Now I can create a Maintenance Plan.
Thanks, Hopefully the rest goes well.
"super1" <superbrownbrown1@.nospam.nospam> wrote in message
news:%23vXvzfO4HHA.2208@.TK2MSFTNGP06.phx.gbl...
>I applied this hotfix pack.
> http://support.microsoft.com/kb/936305
> And it didn't fix the problem. The log has an entry that says
> Product : SQL Server Tools and Workstation Components
> 2005
> Product Version (Previous): 1399
> Product Version (Final) :
> Status : NA
> Log File :
> Error Description : The product instance SQL Tools does not have
> prerequisite update 3042 installed. Update 3175 is dependent on
> prerequisite update 3042. Exit setup and refer to the Knowledge Base
> article to find the prerequisite patch. Install the prerequisite and rerun
> the installation.
> So I need another hotfix first?
> This other hotfix was referenced by Andrew.
> http://support.microsoft.com/kb/933508
> I have requested it from Microsoft but they have not sent it to me yet.
>
> "Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
> news:gDPvcGJ4HHA.4100@.TK2MSFTNGHUB02.phx.gbl...
>> Hi superbrown,
>> Did this issue persist after you installed the patch?
>> Normally this issue should not occur if SQL Server 2005 SP2 was
>> successfully installed. If this issue persists, I recommend that you
>> check
>> if your SQL Server 2005 SP2 had been installed successfully. You can
>> check
>> the setup logs (summary.txt etc) from this folder
>> %ProgramFiles%\Microsoft
>> SQL Server\90\Setup Bootstrap\LOG\Hotfix.
>> If there is no error in the setup log, as a possible workaround, I
>> recommend that just uninstall SQL Server 2005 Client Tools, and then
>> reinstall it and SQL Server 2005 SP2 to see if this issue persists. To
>> uninstall SQL Server 2005 Client Tools, you can refer to the following
>> steps:
>> 1. Open Control Panel -> Add or Remove Programs
>> 2. Select Microsoft SQL Server 2005 from the list, click Remove, just
>> select Workstation Components from the "Remove SQL Server 2005 common
>> components" list, and click Next.
>> 3. Follow the wizard to end the uninstallation.
>> Hope this helps. If this issue persists, I recommend that send the SP2
>> setup logs to me for further research. However the process may need your
>> sending me (changliw_at_microsoft_dot_com) an email response so that I
>> can
>> create a workspace for your uploading the files.
>> If you have any other questions or concerns, please feel free to let me
>> know. It is my pleasure to be of assistance.
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>> =====================================================>> When responding to posts, please "Reply to Group" via
>> your newsreader so that others may learn and benefit
>> from this issue.
>> ======================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> ======================================================>|||Hi SuperBrown,
Thanks for your updating and response.
I am very glad to hear that the suggestions are helpful. If you have any
other questions or encounter any issues in future, please feel free to let
us know.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

Maintenance Cleanup task NOT deleting files

I have applied SP2 and my maintenance cleanup tasks are NOT deleting the files. I have ensured that the folder path is correct. I have also checked the 'age' setting and saved the package. I rebooted the server and ran the job and it still is not deleting the files.

What types of files are not being deleted? I've tested this with backup files (.bak), and it works. I vaguely remember another type of file does not get deleted. Please post more information and we'll figure out next steps.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||

post the result of Select @.@.Version .... After release of SP2, MS has released some fixes for Matinenance Plan and if you have downloaded the SP2 before 05 mar ... then u need to apply those patches

Refer this link : http://support.microsoft.com/kb/933508

if the patch is already applied then the version should be : 9.0.3050.00

Madhu

|||

Yes, we had downloaded SP2 before March 5th, but we saw the release of 2a and have applied it also. The version is , Microsoft SQL Server 2005 - 9.00.3050.00 (Intel X86) Mar 2 2007 20:01:28 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4).

I have also applied 2a to my workstation so my tools version should also be correct.

|||

The file types are the maintenance plan output files, the .txt files. It's the default extension if you select 'maintenance plans files' in the clean up task. The version is Microsoft SQL Server 2005 - 9.00.3050.00 (Intel X86) Mar 2 2007 20:01:28 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4) .

Thanks for any help you can give me.

|||

Mel100 wrote:

The file types are the maintenance plan output files, the .txt files.

As I suspected, this is a known issue that we could not fix in time for Service Pack 2. We ensured that .bak files are deleted properly, but the .txt files are not. See below for the associated Microsoft Connect item. If this scenario is important to you, please vote on it.

https://connect.microsoft.com/feedback/viewfeedback.aspx?FeedbackID=259390&wa=wsignin1.0&siteid=68

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||Thanks so much for your help. This explains the task not deleting the files. I guess until this is fixed we will not use the Maintenance cleanup task.|||

I have a Maintenance Cleanup task that is not deleting bak files. The server connection is valid, the account for the connection is a local admin and the owner of the agent job is a local admin. Local admins have full control to the folder where the files are. Also both accounts have the SA role. I have tried the folder name with a \ at the end and without. The job executes and completes successfully, it just doesn't remove bak files from the folder. I am on SP1 = Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

Any assistance would be appreciated, thanks.

|||

We have the same issue but not in SP2: ver:9.00.2047.00

The trn files are deleted, but the txt not !!

Wednesday, March 21, 2012

Maintenance Cleanup task NOT deleting files

I have applied SP2 and my maintenance cleanup tasks are NOT deleting the files. I have ensured that the folder path is correct. I have also checked the 'age' setting and saved the package. I rebooted the server and ran the job and it still is not deleting the files.

What types of files are not being deleted? I've tested this with backup files (.bak), and it works. I vaguely remember another type of file does not get deleted. Please post more information and we'll figure out next steps.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||

post the result of Select @.@.Version .... After release of SP2, MS has released some fixes for Matinenance Plan and if you have downloaded the SP2 before 05 mar ... then u need to apply those patches

Refer this link : http://support.microsoft.com/kb/933508

if the patch is already applied then the version should be : 9.0.3050.00

Madhu

|||

Yes, we had downloaded SP2 before March 5th, but we saw the release of 2a and have applied it also. The version is , Microsoft SQL Server 2005 - 9.00.3050.00 (Intel X86) Mar 2 2007 20:01:28 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4).

I have also applied 2a to my workstation so my tools version should also be correct.

|||

The file types are the maintenance plan output files, the .txt files. It's the default extension if you select 'maintenance plans files' in the clean up task. The version is Microsoft SQL Server 2005 - 9.00.3050.00 (Intel X86) Mar 2 2007 20:01:28 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4) .

Thanks for any help you can give me.

|||

Mel100 wrote:

The file types are the maintenance plan output files, the .txt files.

As I suspected, this is a known issue that we could not fix in time for Service Pack 2. We ensured that .bak files are deleted properly, but the .txt files are not. See below for the associated Microsoft Connect item. If this scenario is important to you, please vote on it.

https://connect.microsoft.com/feedback/viewfeedback.aspx?FeedbackID=259390&wa=wsignin1.0&siteid=68

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||Thanks so much for your help. This explains the task not deleting the files. I guess until this is fixed we will not use the Maintenance cleanup task.|||

I have a Maintenance Cleanup task that is not deleting bak files. The server connection is valid, the account for the connection is a local admin and the owner of the agent job is a local admin. Local admins have full control to the folder where the files are. Also both accounts have the SA role. I have tried the folder name with a \ at the end and without. The job executes and completes successfully, it just doesn't remove bak files from the folder. I am on SP1 = Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

Any assistance would be appreciated, thanks.

|||

We have the same issue but not in SP2: ver:9.00.2047.00

The trn files are deleted, but the txt not !!