Showing posts with label hotfix. Show all posts
Showing posts with label hotfix. Show all posts

Wednesday, March 21, 2012

Post SQL 2000 SP4 hotfixes - confused??

Hi,
I'm confused with what hotfixes needs to be applied after installing SQL
Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
(FIX: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4) makes sense, but there are
some other hotfixes which I don't know if they need to be applied as well or
not. Those hotfixes are:
836651 (FIX: You receive query results that were not expected when you use
both ANSI joins and non-ANSI joins)
826906 (FIX: A query that uses a view that contains a correlated subquery
and an aggregate runs slowly)
887165 (BUG: You may receive an "Access is denied" error message when a
query calls an extended stored procedure after you upgrade from SQL Server
2000 to SQL Server 2000 Service Pack 4)
Do I have also apply the above hotfixes as well? If yes, then in what
sequence or it doesn't matter?
TIA.
Regards,Rob wrote:
> Hi,
> I'm confused with what hotfixes needs to be applied after installing SQL
> Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
> (FIX: Not all memory is available when AWE is enabled on a computer that is
> running a 32-bit version of SQL Server 2000 SP4) makes sense, but there are
> some other hotfixes which I don't know if they need to be applied as well or
> not. Those hotfixes are:
> 836651 (FIX: You receive query results that were not expected when you use
> both ANSI joins and non-ANSI joins)
> 826906 (FIX: A query that uses a view that contains a correlated subquery
> and an aggregate runs slowly)
> 887165 (BUG: You may receive an "Access is denied" error message when a
> query calls an extended stored procedure after you upgrade from SQL Server
> 2000 to SQL Server 2000 Service Pack 4)
> Do I have also apply the above hotfixes as well? If yes, then in what
> sequence or it doesn't matter?
> TIA.
> Regards,
In general, you should apply any patch that is available. Always apply
them to a development or test server first, let them cook there for a
period of time, then deploy to production. Better to apply them *at
your convenience* than when the place is on fire...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:u3u7XV0qGHA.3248@.TK2MSFTNGP04.phx.gbl...
> Rob wrote:
> > Hi,
> >
> > I'm confused with what hotfixes needs to be applied after installing SQL
> > Server 2000 SP4. One of my server is using AWE so applying hotfix -
899761
> > (FIX: Not all memory is available when AWE is enabled on a computer that
is
> > running a 32-bit version of SQL Server 2000 SP4) makes sense, but there
are
> > some other hotfixes which I don't know if they need to be applied as
well or
> > not. Those hotfixes are:
> >
> > 836651 (FIX: You receive query results that were not expected when you
use
> > both ANSI joins and non-ANSI joins)
> >
> > 826906 (FIX: A query that uses a view that contains a correlated
subquery
> > and an aggregate runs slowly)
> >
> > 887165 (BUG: You may receive an "Access is denied" error message when a
> > query calls an extended stored procedure after you upgrade from SQL
Server
> > 2000 to SQL Server 2000 Service Pack 4)
> >
> > Do I have also apply the above hotfixes as well? If yes, then in what
> > sequence or it doesn't matter?
> >
> > TIA.
> >
> > Regards,
> In general, you should apply any patch that is available.
I will dispute that. And in general Microsoft suggests that you do NOT
apply hot patches unless the fix applies to you. They do not have the full
amount of testing that a service patch has.
> Always apply
> them to a development or test server first, let them cook there for a
> period of time, then deploy to production. Better to apply them *at
> your convenience* than when the place is on fire...
If you do have to apply them, I do agree with this.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Hello, Rob
Hotfixes for SQL Server are cummulative (for the same service pack
level), so if you install a later hotfix there is no need to install
the previous hotfixes.
In particular, the first two KB articles you mentioned (836651 and
826906) correspond to the same post-SP4 hotfix (8.00.2145). However,
the post-SP3 versions of the hotfixes are different (8.00.913 and
8.00.850, respectively), but since those post-SP3 hotfixes were not
included in SP4, another post-SP4 hotfix (i.e. 8.00.2145) was made.
This post-SP4 hotfix was not publicily available, so if you are
affected by those problems, it is recommended to install the
cummulative hotfix build 2187, downloadable from KB article 916287.
This post-SP4 hotfix contains all the post-SP3 hotfixes that were not
included in SP4, the AWE hotfix (and possibly some other hotfixes).
Normally, Microsoft recommends that you do not install any particular
hotfix unless you are affected by that specific problem. However, for
cummulative hotfix build 2187 they did not issue this recommendation,
which makes me believe that this hotfix was more thoroughly tested.
Regarding the last KB article you mentioned, there is no hotfix for
that problem. The KB article 887165 only documents the problem and
provides workarounds.
Razvan

Tuesday, March 20, 2012

Post SQL 2000 SP4 hotfixes - confused??

Hi,
I'm confused with what hotfixes needs to be applied after installing SQL
Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
(FIX: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4) makes sense, but there are
some other hotfixes which I don't know if they need to be applied as well or
not. Those hotfixes are:
836651 (FIX: You receive query results that were not expected when you use
both ANSI joins and non-ANSI joins)
826906 (FIX: A query that uses a view that contains a correlated subquery
and an aggregate runs slowly)
887165 (BUG: You may receive an "Access is denied" error message when a
query calls an extended stored procedure after you upgrade from SQL Server
2000 to SQL Server 2000 Service Pack 4)
Do I have also apply the above hotfixes as well? If yes, then in what
sequence or it doesn't matter?
TIA.
Regards,Rob wrote:
> Hi,
> I'm confused with what hotfixes needs to be applied after installing SQL
> Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
> (FIX: Not all memory is available when AWE is enabled on a computer that i
s
> running a 32-bit version of SQL Server 2000 SP4) makes sense, but there ar
e
> some other hotfixes which I don't know if they need to be applied as well
or
> not. Those hotfixes are:
> 836651 (FIX: You receive query results that were not expected when you use
> both ANSI joins and non-ANSI joins)
> 826906 (FIX: A query that uses a view that contains a correlated subquery
> and an aggregate runs slowly)
> 887165 (BUG: You may receive an "Access is denied" error message when a
> query calls an extended stored procedure after you upgrade from SQL Server
> 2000 to SQL Server 2000 Service Pack 4)
> Do I have also apply the above hotfixes as well? If yes, then in what
> sequence or it doesn't matter?
> TIA.
> Regards,
In general, you should apply any patch that is available. Always apply
them to a development or test server first, let them cook there for a
period of time, then deploy to production. Better to apply them *at
your convenience* than when the place is on fire...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:u3u7XV0qGHA.3248@.TK2MSFTNGP04.phx.gbl...
> Rob wrote:
899761[vbcol=seagreen]
is[vbcol=seagreen]
are[vbcol=seagreen]
well or[vbcol=seagreen]
use[vbcol=seagreen]
subquery[vbcol=seagreen]
Server[vbcol=seagreen]
> In general, you should apply any patch that is available.
I will dispute that. And in general Microsoft suggests that you do NOT
apply hot patches unless the fix applies to you. They do not have the full
amount of testing that a service patch has.

> Always apply
> them to a development or test server first, let them cook there for a
> period of time, then deploy to production. Better to apply them *at
> your convenience* than when the place is on fire...
If you do have to apply them, I do agree with this.

>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Hello, Rob
Hotfixes for SQL Server are cummulative (for the same service pack
level), so if you install a later hotfix there is no need to install
the previous hotfixes.
In particular, the first two KB articles you mentioned (836651 and
826906) correspond to the same post-SP4 hotfix (8.00.2145). However,
the post-SP3 versions of the hotfixes are different (8.00.913 and
8.00.850, respectively), but since those post-SP3 hotfixes were not
included in SP4, another post-SP4 hotfix (i.e. 8.00.2145) was made.
This post-SP4 hotfix was not publicily available, so if you are
affected by those problems, it is recommended to install the
cummulative hotfix build 2187, downloadable from KB article 916287.
This post-SP4 hotfix contains all the post-SP3 hotfixes that were not
included in SP4, the AWE hotfix (and possibly some other hotfixes).
Normally, Microsoft recommends that you do not install any particular
hotfix unless you are affected by that specific problem. However, for
cummulative hotfix build 2187 they did not issue this recommendation,
which makes me believe that this hotfix was more thoroughly tested.
Regarding the last KB article you mentioned, there is no hotfix for
that problem. The KB article 887165 only documents the problem and
provides workarounds.
Razvan

Post SP4 Hotfix

Can anyone help me to get the hotfix SQL Server 2000 build 8.00.2215 ?
As i do not find any download link.According to http://www.sqlsecurity.com/ (check FAQs, version database), this is a PSS release only. That means that you will have to contact MS and specifically request the patch.

There is no charge for the phone call (at least not last time I had to do this).

Regards,

hmscott|||http://support.microsoft.com/kb/894905|||http://support.microsoft.com/kb/924662/
http://support.microsoft.com/kb/936232/

post SP1 hotfix

Just curious, I'm reading about the SQL Server 2005 post SP1 hotfix and it looks like you need to install the packages in order:

SQL Server

Analysis Services

Integration Services

Notification Services

Reporting Services

Tools

My desktop is configured as an Analysis Services and Integration Services instance, but without the SQL Server proper components installed. What should my install order be? Does important note 3 about SMO and SQL-DMO still apply?

Thanks,

Keehan

What document do you refer to?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Sorry 'bout that:

http://support.microsoft.com/kb/918222

Cheers,

Keehan

|||

If you didnt install SQL Server relational engine, you should be fine with installing hotfix packges for installed components only.

Looks SQL-DMO issue only applies if you have SQL Server relational engine installed.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Post SP Install issue

We have a active/active W2K3 SQL cluster with 3 instances that was upgraded
to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
problems.
However, when applying the hotix only the first instance upgraded correctly.
The hotfix install for instances 2 and 3 indicated success but the version
for both still shows build 2139. Can't seem to get the install to work for
these instances. Any help would be appreciated.Hi
You may want to re-contact PSS for this as this is a PSS only hotfix!
John
"GManino" wrote:
> We have a active/active W2K3 SQL cluster with 3 instances that was upgraded
> to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
> problems.
> However, when applying the hotix only the first instance upgraded correctly.
> The hotfix install for instances 2 and 3 indicated success but the version
> for both still shows build 2139. Can't seem to get the install to work for
> these instances. Any help would be appreciated.|||Hi
Your answer is Windows Task Scheduler.
See http://msmvps.com/epprecht/archive/2005/08/28/64380.aspx
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"GManino" <GManino@.discussions.microsoft.com> wrote in message
news:9BBD59DE-12E8-4A0C-AA9B-61B25D031BB3@.microsoft.com...
> We have a active/active W2K3 SQL cluster with 3 instances that was
> upgraded
> to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
> problems.
> However, when applying the hotix only the first instance upgraded
> correctly.
> The hotfix install for instances 2 and 3 indicated success but the version
> for both still shows build 2139. Can't seem to get the install to work
> for
> these instances. Any help would be appreciated.|||Does anyone know if this will work for all types of corruption?
"John Bell" wrote:
> Hi
> You may want to re-contact PSS for this as this is a PSS only hotfix!
> John
> "GManino" wrote:
> > We have a active/active W2K3 SQL cluster with 3 instances that was upgraded
> > to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
> > problems.
> >
> > However, when applying the hotix only the first instance upgraded correctly.
> > The hotfix install for instances 2 and 3 indicated success but the version
> > for both still shows build 2139. Can't seem to get the install to work for
> > these instances. Any help would be appreciated.

Post SP Install issue

We have a active/active W2K3 SQL cluster with 3 instances that was upgraded
to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
problems.
However, when applying the hotix only the first instance upgraded correctly.
The hotfix install for instances 2 and 3 indicated success but the version
for both still shows build 2139. Can't seem to get the install to work for
these instances. Any help would be appreciated.
Hi
You may want to re-contact PSS for this as this is a PSS only hotfix!
John
"GManino" wrote:

> We have a active/active W2K3 SQL cluster with 3 instances that was upgraded
> to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
> problems.
> However, when applying the hotix only the first instance upgraded correctly.
> The hotfix install for instances 2 and 3 indicated success but the version
> for both still shows build 2139. Can't seem to get the install to work for
> these instances. Any help would be appreciated.
|||Hi
Your answer is Windows Task Scheduler.
See http://msmvps.com/epprecht/archive/2.../28/64380.aspx
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"GManino" <GManino@.discussions.microsoft.com> wrote in message
news:9BBD59DE-12E8-4A0C-AA9B-61B25D031BB3@.microsoft.com...
> We have a active/active W2K3 SQL cluster with 3 instances that was
> upgraded
> to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
> problems.
> However, when applying the hotix only the first instance upgraded
> correctly.
> The hotfix install for instances 2 and 3 indicated success but the version
> for both still shows build 2139. Can't seem to get the install to work
> for
> these instances. Any help would be appreciated.
|||Does anyone know if this will work for all types of corruption?
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You may want to re-contact PSS for this as this is a PSS only hotfix!
> John
> "GManino" wrote:

Post SP Install issue

We have a active/active W2K3 SQL cluster with 3 instances that was upgraded
to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
problems.
However, when applying the hotix only the first instance upgraded correctly.
The hotfix install for instances 2 and 3 indicated success but the version
for both still shows build 2139. Can't seem to get the install to work for
these instances. Any help would be appreciated.Hi
You may want to re-contact PSS for this as this is a PSS only hotfix!
John
"GManino" wrote:

> We have a active/active W2K3 SQL cluster with 3 instances that was upgrade
d
> to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
> problems.
> However, when applying the hotix only the first instance upgraded correctl
y.
> The hotfix install for instances 2 and 3 indicated success but the versio
n
> for both still shows build 2139. Can't seem to get the install to work fo
r
> these instances. Any help would be appreciated.|||Hi
Your answer is Windows Task Scheduler.
See http://msmvps.com/epprecht/archive/...8/28/64380.aspx
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"GManino" <GManino@.discussions.microsoft.com> wrote in message
news:9BBD59DE-12E8-4A0C-AA9B-61B25D031BB3@.microsoft.com...
> We have a active/active W2K3 SQL cluster with 3 instances that was
> upgraded
> to SP4 with the 2148 hotfix. All 3 instances upgraded to SP 4 with no
> problems.
> However, when applying the hotix only the first instance upgraded
> correctly.
> The hotfix install for instances 2 and 3 indicated success but the version
> for both still shows build 2139. Can't seem to get the install to work
> for
> these instances. Any help would be appreciated.|||Does anyone know if this will work for all types of corruption?
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You may want to re-contact PSS for this as this is a PSS only hotfix!
> John
> "GManino" wrote:
>

Post Hotfix error

I am getting the following (MOM) error on 3 of my databases anytime I initiate a backup of the mdf. The database seems to backup as expected. The one thing that has recently changed is I implemented MS Hotfix 2187 on my SQl cluster over the weekend.

Severity: Critical Error

Status: New

Source: MSSQLSERVER

Name: Commit record has already been distributed. Check DBTABLE

Description: Unable to expand message 17055 [-1073724769] 18264 Database backed up: Database: XX03PLUS, creation date(time): 2005/12/06(18:38:50), pages dumped: 23026, first LSN: 18761:44:1, last LSN: 18761:46:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\temp\ar03PLUS_fromVCforK1.bak'}).

thanks in advance,

Jerry

I thought I would reply to my own post as I have remediated the error in case someone else ever has this issue.

AS it turns out the Hotfix 'upgrade' can create orphaned users and or users with 'not as expected' permissions. By deinstalling (detaching) and reinstalling (re-attaching) via an internal script that also reassigned appropriate users and permissions I wa able to clean up the errors.

best of luck,

Jerry