Re: Hotfix question

From: bob jones (utefan001@yahoo.com)
Date: 01/28/03


From: "bob jones" <utefan001@yahoo.com>
Date: Tue, 28 Jan 2003 11:14:12 -0800


I have not applied this patch yet, but Q319212 says
that "To resolve this problem, contact Microsoft Product
Support Services to obtain the fix." (I have done
this) "You must apply this hotfix to a server that is
running SQL Server 7.0 Service Pack 3. This fix will not
be available in Service Pack 4; however, it will be made
available in a post-SP4 build."

I would assume that the latest Cumulative Patch for SQL
Server (Q316333) (Originally posted: October 02, 2002) has
my fix (Q319212) included, but I have not been able to
verify this is writing. If you have a document or link
you can point me to, that would be most helpful.
Thanks

>-----Original Message-----
>Have you applied the patch from
>
>http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/security/
>bulletin/MS02-056.asp
>
>It should have your fix as well as the security fixes.
>
>--
>Richard Waymire, MCSE, MCDBA
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Richard Waymire [MS]" <rwaymi@online.microsoft.com>
wrote in message
>news:OwH5APvxCHA.2528@TK2MSFTNGP09...
>> I'll check and see if I can find more info.
>>
>> --
>> Richard Waymire, MCSE, MCDBA
>>
>> This posting is provided "AS IS" with no warranties,
and confers no
>rights.
>> "bob jones" <utefan001@yahoo.com> wrote in message
>> news:066901c2c6ea$288b9b40$8df82ecf@TK2MSFTNGXA02...
>> > About a year ago, I submitted a bug to Microsoft SQL
>> > Support. After a short time, I was told that this
was an
>> > bug and Microsoft would build a hotfix.
>> > See: http://support.microsoft.com/default.aspx?
scid=kb%
>> > 3Ben-us%3B319212
>> >
>> > The instructions from Microsoft (below) led me to
believe
>> > that applying any service pack or security fix would
undo
>> > this hotfix that is mission critical to our
datacenter.
>> >
>> > The package includes a README.TXT with details about
how
>> > to install the hotfix. This fix requires that SQL
7.0 SP3
>> > already be installed on the server. We are beyond the
>> > cutoff date for fixes to make it into SP4 (currently
in
>> > beta), so this fix will also be addressed in a post-
SP4
>> > QFE rollup build to be released after SP4. In other
>> > words, when SP4 comes out, don&#8217;t apply it until you
have
>> > the SP4 QFE rollup build because SP4 itself will not
>> > include this fix.
>> >
>> > Does anyone know if the SP4 QFE build exits yet or if
I
>> > can apply SQL 7 security fixes without breaking my
>> > hotfix? This is not something I can easily test
because
>> > the hotfix fixes a production problem when the server
is
>> > under a heavy load.
>> >
>> > Thanks
>>
>>
>
>
>.
>



Relevant Pages

  • Re: Recovery Storage Group: Invalid DN Syntax Error on names with
    ... Please contact Microsoft directly to receive a hotfix. ... Here is the fix. ... >> password for each package. ...
    (microsoft.public.exchange.admin)
  • Re: Q811493 hotfix
    ... after installing the Q811493 hotfix. ... Hopefully we'll see a fix soon. ... >Microsoft has stated they are working on the cause, ... >> Windows Update, installing the Q811493 update as suggested. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Event 1000 Windows SharePoint Services 2.0 Error
    ... I wonder how hard it would be for Microsoft to post the fix. ... the the SP1 version of SQL had gone into the four or five instances of MSDE ... I am tired of telling my server to NOT INSTALL 948110. ...
    (microsoft.public.windows.server.sbs)
  • RE: Event ID 61 in Print Server
    ... After you install the hotfix that is described in this article, ... obtain the latest service pack for Microsoft ... A supported fix is now available from Microsoft, but it is only intended to ... contact Microsoft Product Support ...
    (microsoft.public.win2000.printing)
  • Re: Oops, heres the link - Re: Event ID: 5504
    ... I'll give Microsoft a call tomorrow and take it from there. ... The normal method for obtaining a hotfix would be to contact ... >> I did check out that hot fix link but I thought it was fixed in SP4 ...
    (microsoft.public.windows.server.dns)