SQL2K cumulative/rollup hotfix build 2187 stable?

Does anyone know when exactly this cumulative hotfix was first released, as
dates on MS KB articles change as the article is updated, making it difficul
t
to tell?

More importantly, is it stable.  For example, the SQL2K cumulative
hotfix/security rollup build 818 was the standard for quite some time, so
would the quality of this rollup fit into this category?

Any problems pointed out that were experienced post installation (especially
on a cluster) would help greatly.  Thanks.

Can't say when it was released, but when I was at PSS, I never had any
issues with it.

.2162 was horrible...

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com


"DisgruntledTechGuy" < DisgruntledTechGuy@d
iscussions.microsoft.com> wrote in
message news:DE58E0E3-4101-4DF0-BD5C- FAAC0EEC5770@microso
ft.com...
> Does anyone know when exactly this cumulative hotfix was first released,
> as
> dates on MS KB articles change as the article is updated, making it
> difficult
> to tell?
>
> More importantly, is it stable.  For example, the SQL2K cumulative
> hotfix/security rollup build 818 was the standard for quite some time, so
> would the quality of this rollup fit into this category?
>
> Any problems pointed out that were experienced post installation
> (especially
> on a cluster) would help greatly.  Thanks.

Kevin, thanks for the inside scoop.  I was able to figure out from this link
(http://www.microsoft.com/downloads/...&displaylang=en)
that build 2187 was released on 03/23/2006.  I could not find anything about
the availability/download of build 2162, other than that it has been
superceded by build 2187 - yes, seems MS really wants us to forget about tha
t
one as all its links point to build 2187...

"Kevin3NF" wrote:

> Can't say when it was released, but when I was at PSS, I never had any
> issues with it.
>
> ..2162 was horrible...
>
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> http://kevin3nf.blogspot.com
>
>
> "DisgruntledTechGuy" < DisgruntledTechGuy@d
iscussions.microsoft.com> wrote 
in
> message news:DE58E0E3-4101-4DF0-BD5C- FAAC0EEC5770@microso
ft.com... 
>
>
>