An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services 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 cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, 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?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.
*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services 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 cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, 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?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
Showing posts with label cleanup. Show all posts
Showing posts with label cleanup. Show all posts
Friday, March 30, 2012
Microsoft SQL Server 2005 SP2 Issue
An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services 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 cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, 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?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.
*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:OGpfQVFYHHA.4368@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services 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 cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, 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?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services 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 cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, 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?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.
*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:OGpfQVFYHHA.4368@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services 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 cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, 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?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
Microsoft SQL Server 2005 SP2 Issue
An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services 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 cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, 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?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services 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 cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, 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?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services 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 cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, 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?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services 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 cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, 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?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
Microsoft SQL Server 2005 SP2 Issue
An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services 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 cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, 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?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services 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 cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, 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?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services 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 cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, 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?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services 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 cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, 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?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
Wednesday, March 7, 2012
Metadata cleanup has deleted metadata at the Subscriber incorrectly?
Hi,
We have Microsoft SQL Server 2005 SP1 based merge replication application. This system consist of 1 publisher/distributor and about 700 subscribers. Publisher is MS SQL Server 2005 standard SP1 and subscribers are mostly MS SQL Server Express SP1s.
We started this system in September last year with migrating data as region based with one area at time. Everything went well until January 2007 when over 500 users were using new system. What is even strange that most errors comes on areas which were moved to new system on week number 2 on 2007 (8.1.2007->)
I have double and cross checked that these publications have exact the same parameteters as working publications.
The error message which comes on subscriber is following:
The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Subscriber for changes not yet sent to the Publisher. You must reinitialize the subscription (without upload). (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199401) Get help: http://help/MSSQL_REPL-2147199401
When this error comes client subscription should not be expired yet. So subscription is expiring incorrectly earlier than expected. After reinit subcriber can syncronize without any errors. For now machines suffering of this error have been different machines so there is no certain information if this error is repeatable on same machine.
Real bad thing is that if user has't syncronized in regular basis there is possibility to that data may be lost because the reinit must be done without upload as error message says.
Regards,
Jouko
We have now installed SP2 to over 650 machines and we are still getting this error. So it seems obvious that SP2 do NOT fix this error. We have now open second time support case to Microsoft about this issue. First time we got answer to apply SP2 to all machines that are involved with replication.
Jouko
metadata cleanup 2147199401
Hi,
I'm getting the following error on SQL Server 2005
Error messages:
The Merge Agent failed after detecting that retention-based metadata cleanup
has deleted metadata at the Subscriber for changes not yet sent to the
Publisher. You must reinitialize the subscription (without upload). (Source:
MSSQL_REPL, Error number: MSSQL_REPL-2147199401)
Get help: http://help/MSSQL_REPL-2147199401
The subscription has been running fine for several months and re
initialising is painful due to the size of the DB and the connection speed.
Has anyone encountered this error or know of a fix?
Thanks
NW
There seems to be a bug with this that Microsoft is in the process of trying
to fix (from what I understand). I suggest you open a support incident with
Microsoft on this.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"NeilWake" <NeilWake@.discussions.microsoft.com> wrote in message
news:A8E78C08-E908-4D41-A03B-A5BE807C7D7C@.microsoft.com...
> Hi,
> I'm getting the following error on SQL Server 2005
> Error messages:
> The Merge Agent failed after detecting that retention-based metadata
> cleanup
> has deleted metadata at the Subscriber for changes not yet sent to the
> Publisher. You must reinitialize the subscription (without upload).
> (Source:
> MSSQL_REPL, Error number: MSSQL_REPL-2147199401)
> Get help: http://help/MSSQL_REPL-2147199401
> The subscription has been running fine for several months and re
> initialising is painful due to the size of the DB and the connection
> speed.
> Has anyone encountered this error or know of a fix?
> Thanks
> NW
>
I'm getting the following error on SQL Server 2005
Error messages:
The Merge Agent failed after detecting that retention-based metadata cleanup
has deleted metadata at the Subscriber for changes not yet sent to the
Publisher. You must reinitialize the subscription (without upload). (Source:
MSSQL_REPL, Error number: MSSQL_REPL-2147199401)
Get help: http://help/MSSQL_REPL-2147199401
The subscription has been running fine for several months and re
initialising is painful due to the size of the DB and the connection speed.
Has anyone encountered this error or know of a fix?
Thanks
NW
There seems to be a bug with this that Microsoft is in the process of trying
to fix (from what I understand). I suggest you open a support incident with
Microsoft on this.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"NeilWake" <NeilWake@.discussions.microsoft.com> wrote in message
news:A8E78C08-E908-4D41-A03B-A5BE807C7D7C@.microsoft.com...
> Hi,
> I'm getting the following error on SQL Server 2005
> Error messages:
> The Merge Agent failed after detecting that retention-based metadata
> cleanup
> has deleted metadata at the Subscriber for changes not yet sent to the
> Publisher. You must reinitialize the subscription (without upload).
> (Source:
> MSSQL_REPL, Error number: MSSQL_REPL-2147199401)
> Get help: http://help/MSSQL_REPL-2147199401
> The subscription has been running fine for several months and re
> initialising is painful due to the size of the DB and the connection
> speed.
> Has anyone encountered this error or know of a fix?
> Thanks
> NW
>
Meta Data Cleanup For Merge Repl.
I am wondering specifically when the changes on the Publisher are cleaned
up. I have implemented merge replication with each publication having a
retention time (set in sp_addmergepublication) of 18 months and a
@.max_disretention (set in sp_adddistributiondb) also at 18 months. Also I
have a system where there is 1 Subscription PER Publication. The
Subscribers can be disconnected for long periods of time (I'm hoping for
less than 18 months). Now the changes on the Publisher will be stored on
the Distributor and will wait until a PULL Subscriber connects to Merge the
changes (changes made on both sides). From what I understand the merge
agent controls the meta data and will clean up the stored changes on the
distributor depending on the Retention period of the publication. So at
each merge agent run, anything older than 18 months that whether or not it
has been merged will be cleaned up (the max_disretention gets rid of changes
that have not been applied to subscribers too). Is this basically how the
cleanup of changes works?
When a connection is made I have a script that can be run to reinitialize a
subscription. It basically runs the merge agent, starts the snapshot agent,
sets the subscription to be reinitialized, and then runs the merge agent
again to apply the snapshot. Will Reinitializing a subscription clean up
the changes for a publication, kind of override the retention period?
Any ideas as to when the Change log (change info stored for a merge) is
cleaned up?
thanks,
Nate
Oops, the Distribution DB doesn't do anything during merge replication so
min_distretention and max_distretention don't apply. Just the Retention
period of the Publications. Can anyone confirm that the MetaData is only
cleaned up by the merge agent using the Retention period? And, that the
data is not cleaned up when a subscription is reinitialized?
thanks,
nate
up. I have implemented merge replication with each publication having a
retention time (set in sp_addmergepublication) of 18 months and a
@.max_disretention (set in sp_adddistributiondb) also at 18 months. Also I
have a system where there is 1 Subscription PER Publication. The
Subscribers can be disconnected for long periods of time (I'm hoping for
less than 18 months). Now the changes on the Publisher will be stored on
the Distributor and will wait until a PULL Subscriber connects to Merge the
changes (changes made on both sides). From what I understand the merge
agent controls the meta data and will clean up the stored changes on the
distributor depending on the Retention period of the publication. So at
each merge agent run, anything older than 18 months that whether or not it
has been merged will be cleaned up (the max_disretention gets rid of changes
that have not been applied to subscribers too). Is this basically how the
cleanup of changes works?
When a connection is made I have a script that can be run to reinitialize a
subscription. It basically runs the merge agent, starts the snapshot agent,
sets the subscription to be reinitialized, and then runs the merge agent
again to apply the snapshot. Will Reinitializing a subscription clean up
the changes for a publication, kind of override the retention period?
Any ideas as to when the Change log (change info stored for a merge) is
cleaned up?
thanks,
Nate
Oops, the Distribution DB doesn't do anything during merge replication so
min_distretention and max_distretention don't apply. Just the Retention
period of the Publications. Can anyone confirm that the MetaData is only
cleaned up by the merge agent using the Retention period? And, that the
data is not cleaned up when a subscription is reinitialized?
thanks,
nate
Meta Data Cleanup Error
Hi,
We are Merge replicating about 50 Production databases. We had planned to
monitor the meta deta clean up error during replication.
While we were monitoring the data to be updated during replication in one of
these databases, noticed 4 records to be merge replicated ( 3 insert and 1
update). At this moment we noticed the meta data clean up error. "The merge
process could not perform retention-based meta data cleanup in database
'database name'". The replication was in retrying mode and additionally the
following errors were reported
a) The subscription to publication 'XXXX' is invalid.
b) The process is running and is waiting for a response from one of the
backend connections'
During this process there we no issues in the remaining 49 databases,
replication was proceeding as usual.
In this database where we noticed the the above errors, the replication was
in sync in another 10 minutes, without any manual intervention.
What triggers to raise these error messages.
Please let us know what correction action we need to take for these error
messages
Thanks,
Soura.
Hi,
I got it from One article...
"The most common reason I can think of is that the query timed out. Sometime
retention based cleaup may need to cleanup a lot of rows and that can take
time. Rerunning the merge with a larger value for the querytimeout parameter
should fix this problem."
Hope this will help
Herbert
"SouRa" wrote:
> Hi,
> We are Merge replicating about 50 Production databases. We had planned to
> monitor the meta deta clean up error during replication.
> While we were monitoring the data to be updated during replication in one of
> these databases, noticed 4 records to be merge replicated ( 3 insert and 1
> update). At this moment we noticed the meta data clean up error. "The merge
> process could not perform retention-based meta data cleanup in database
> 'database name'". The replication was in retrying mode and additionally the
> following errors were reported
> a) The subscription to publication 'XXXX' is invalid.
> b) The process is running and is waiting for a response from one of the
> backend connections'
> During this process there we no issues in the remaining 49 databases,
> replication was proceeding as usual.
> In this database where we noticed the the above errors, the replication was
> in sync in another 10 minutes, without any manual intervention.
> What triggers to raise these error messages.
> Please let us know what correction action we need to take for these error
> messages
> Thanks,
> Soura.
We are Merge replicating about 50 Production databases. We had planned to
monitor the meta deta clean up error during replication.
While we were monitoring the data to be updated during replication in one of
these databases, noticed 4 records to be merge replicated ( 3 insert and 1
update). At this moment we noticed the meta data clean up error. "The merge
process could not perform retention-based meta data cleanup in database
'database name'". The replication was in retrying mode and additionally the
following errors were reported
a) The subscription to publication 'XXXX' is invalid.
b) The process is running and is waiting for a response from one of the
backend connections'
During this process there we no issues in the remaining 49 databases,
replication was proceeding as usual.
In this database where we noticed the the above errors, the replication was
in sync in another 10 minutes, without any manual intervention.
What triggers to raise these error messages.
Please let us know what correction action we need to take for these error
messages
Thanks,
Soura.
Hi,
I got it from One article...
"The most common reason I can think of is that the query timed out. Sometime
retention based cleaup may need to cleanup a lot of rows and that can take
time. Rerunning the merge with a larger value for the querytimeout parameter
should fix this problem."
Hope this will help
Herbert
"SouRa" wrote:
> Hi,
> We are Merge replicating about 50 Production databases. We had planned to
> monitor the meta deta clean up error during replication.
> While we were monitoring the data to be updated during replication in one of
> these databases, noticed 4 records to be merge replicated ( 3 insert and 1
> update). At this moment we noticed the meta data clean up error. "The merge
> process could not perform retention-based meta data cleanup in database
> 'database name'". The replication was in retrying mode and additionally the
> following errors were reported
> a) The subscription to publication 'XXXX' is invalid.
> b) The process is running and is waiting for a response from one of the
> backend connections'
> During this process there we no issues in the remaining 49 databases,
> replication was proceeding as usual.
> In this database where we noticed the the above errors, the replication was
> in sync in another 10 minutes, without any manual intervention.
> What triggers to raise these error messages.
> Please let us know what correction action we need to take for these error
> messages
> Thanks,
> Soura.
meta data cleanup
Hi
I am running a couple of sql 2000 SP3a servers with merge and snapshot
replication. One server acting as publisher and distributor and the rest
subscribers. On one of the server I have got the error below and have tried
most of the suggestions by msdn. This server has not crashed ever before or
any hardware problems. It has been running for a couple of months and no
problems. This has not happened no any of the other servers. Any
suggestions would be greatly appreciated as the only resolution I have left
is to bring up a new instance, setup replication and see if this would
resolve the issue. Thanx
Server: EASTSRV3
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[4/14/2005 12:57:26 PM]EASTSRV3.ICASData: {call sp_MSgetversion }
Percent Complete: 2
Connecting to Subscriber 'EASTSRV3'
Percent Complete: 3
Retrieving publication information
Percent Complete: 4
Retrieving subscription information
Percent Complete: 4
The merge process is cleaning up meta data in database 'HO_Master'.
Percent Complete: 4
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
Percent Complete: 4
The merge process is cleaning up meta data in database 'ICASData'.
The merge process could not perform retention-based meta data cleanup in
database 'ICASData'.
Percent Complete: 0
The merge process could not perform retention-based meta data cleanup in
database 'ICASData'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147199467
Message: The merge process could not perform retention-based meta data
cleanup in database 'ICASData'.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_mergemetadataretentioncleanup(?, ?, ?)}
Percent Complete: 0
Category:SQLSERVER
Source: EASTSRV3
Number: 11
Message: General network error. Check your network documentation.
Message posted via http://www.sqlmonster.com
Jayanthi from MS posted this before:
"The most common reason I can think of is that the query timed out. Sometime
retention based cleaup may need to cleanup a lot of rows and that can take
time. Rerunning the merge with a larger value for the querytimeout parameter
should fix this problem."
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul
Thanx for the reply.
I have played with the agent profiles aswell. From default to 1800. This
has been going on for like two days now no synch at all. I have tried to
reindex also as this was also one of the msdn suggestions.
Message posted via http://www.sqlmonster.com
I am running a couple of sql 2000 SP3a servers with merge and snapshot
replication. One server acting as publisher and distributor and the rest
subscribers. On one of the server I have got the error below and have tried
most of the suggestions by msdn. This server has not crashed ever before or
any hardware problems. It has been running for a couple of months and no
problems. This has not happened no any of the other servers. Any
suggestions would be greatly appreciated as the only resolution I have left
is to bring up a new instance, setup replication and see if this would
resolve the issue. Thanx
Server: EASTSRV3
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[4/14/2005 12:57:26 PM]EASTSRV3.ICASData: {call sp_MSgetversion }
Percent Complete: 2
Connecting to Subscriber 'EASTSRV3'
Percent Complete: 3
Retrieving publication information
Percent Complete: 4
Retrieving subscription information
Percent Complete: 4
The merge process is cleaning up meta data in database 'HO_Master'.
Percent Complete: 4
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
Percent Complete: 4
The merge process is cleaning up meta data in database 'ICASData'.
The merge process could not perform retention-based meta data cleanup in
database 'ICASData'.
Percent Complete: 0
The merge process could not perform retention-based meta data cleanup in
database 'ICASData'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147199467
Message: The merge process could not perform retention-based meta data
cleanup in database 'ICASData'.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_mergemetadataretentioncleanup(?, ?, ?)}
Percent Complete: 0
Category:SQLSERVER
Source: EASTSRV3
Number: 11
Message: General network error. Check your network documentation.
Message posted via http://www.sqlmonster.com
Jayanthi from MS posted this before:
"The most common reason I can think of is that the query timed out. Sometime
retention based cleaup may need to cleanup a lot of rows and that can take
time. Rerunning the merge with a larger value for the querytimeout parameter
should fix this problem."
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul
Thanx for the reply.
I have played with the agent profiles aswell. From default to 1800. This
has been going on for like two days now no synch at all. I have tried to
reindex also as this was also one of the msdn suggestions.
Message posted via http://www.sqlmonster.com
Meta Data cleanup
I have a quick question that I could not find the answer for anywhere.
The software developers that provided our SQL database program advised us to
put the subscription expiration on "never expire" because of their past
experience with customers who do not maintain their databases. Because of
this we now how massive meta data tables that need to be purged to increase
replkication performance (synchronization is extrmely slow). I have tried
setting the subscription retention to 14 days, but the amount of data to be
purged is huge and it interferes with the synchroniztion over night.
What I would like to do is use the stored procedure
sp_mergemetadataretentioncleanup to individually clean up the meta data
tables at each subscriber and the publisher. My problem is that I can not
find the parameters and correct syntax for this procedure anywhere. I have
seen the following:
sp_mergemetadataretentioncleanup (?,?,?)
but I don't know what to use to fill the question mark. I'm assuming I need
parameters since it seems doubtful the procedure is complete in itself (I'm
guessing a parameter is retention time and probably database?).
Thanks for the help.
Pete
these are output parameters.
declare @.num_genhistory_rows int , @.num_contents_rows int ,
@.num_tombstone_rows int
exec sp_mergemetadataretentioncleanup @.num_genhistory_rows output,
@.num_contents_rows output, @.num_tombstone_rows output
print @.num_genhistory_rows
print @.num_contents_rows
print @.num_tombstone_rows
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pete" <Pete@.discussions.microsoft.com> wrote in message
news:C19A9C44-1298-4AC0-8088-57D4ED4DD799@.microsoft.com...
> I have a quick question that I could not find the answer for anywhere.
> The software developers that provided our SQL database program advised us
to
> put the subscription expiration on "never expire" because of their past
> experience with customers who do not maintain their databases. Because of
> this we now how massive meta data tables that need to be purged to
increase
> replkication performance (synchronization is extrmely slow). I have tried
> setting the subscription retention to 14 days, but the amount of data to
be
> purged is huge and it interferes with the synchroniztion over night.
> What I would like to do is use the stored procedure
> sp_mergemetadataretentioncleanup to individually clean up the meta data
> tables at each subscriber and the publisher. My problem is that I can not
> find the parameters and correct syntax for this procedure anywhere. I have
> seen the following:
> sp_mergemetadataretentioncleanup (?,?,?)
> but I don't know what to use to fill the question mark. I'm assuming I
need
> parameters since it seems doubtful the procedure is complete in itself
(I'm
> guessing a parameter is retention time and probably database?).
> Thanks for the help.
> Pete
The software developers that provided our SQL database program advised us to
put the subscription expiration on "never expire" because of their past
experience with customers who do not maintain their databases. Because of
this we now how massive meta data tables that need to be purged to increase
replkication performance (synchronization is extrmely slow). I have tried
setting the subscription retention to 14 days, but the amount of data to be
purged is huge and it interferes with the synchroniztion over night.
What I would like to do is use the stored procedure
sp_mergemetadataretentioncleanup to individually clean up the meta data
tables at each subscriber and the publisher. My problem is that I can not
find the parameters and correct syntax for this procedure anywhere. I have
seen the following:
sp_mergemetadataretentioncleanup (?,?,?)
but I don't know what to use to fill the question mark. I'm assuming I need
parameters since it seems doubtful the procedure is complete in itself (I'm
guessing a parameter is retention time and probably database?).
Thanks for the help.
Pete
these are output parameters.
declare @.num_genhistory_rows int , @.num_contents_rows int ,
@.num_tombstone_rows int
exec sp_mergemetadataretentioncleanup @.num_genhistory_rows output,
@.num_contents_rows output, @.num_tombstone_rows output
print @.num_genhistory_rows
print @.num_contents_rows
print @.num_tombstone_rows
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pete" <Pete@.discussions.microsoft.com> wrote in message
news:C19A9C44-1298-4AC0-8088-57D4ED4DD799@.microsoft.com...
> I have a quick question that I could not find the answer for anywhere.
> The software developers that provided our SQL database program advised us
to
> put the subscription expiration on "never expire" because of their past
> experience with customers who do not maintain their databases. Because of
> this we now how massive meta data tables that need to be purged to
increase
> replkication performance (synchronization is extrmely slow). I have tried
> setting the subscription retention to 14 days, but the amount of data to
be
> purged is huge and it interferes with the synchroniztion over night.
> What I would like to do is use the stored procedure
> sp_mergemetadataretentioncleanup to individually clean up the meta data
> tables at each subscriber and the publisher. My problem is that I can not
> find the parameters and correct syntax for this procedure anywhere. I have
> seen the following:
> sp_mergemetadataretentioncleanup (?,?,?)
> but I don't know what to use to fill the question mark. I'm assuming I
need
> parameters since it seems doubtful the procedure is complete in itself
(I'm
> guessing a parameter is retention time and probably database?).
> Thanks for the help.
> Pete
Subscribe to:
Posts (Atom)