Greetings.
Apparently the fix described in article 826906 ("A query that uses a view
that contains a correlated subquery and an aggregate runs slowly") didn't
make it into SP4.
I think I'm getting bitten by this, and don't have an easy way to rewrite
the query (it's generated by Analysis Services). Is there any ETA for a
corresponding hotfix to be released for SP4?
Regards,
JonathanHello,
The final release of this hotfix for SP4 has not been determined. If there
is any update we will let you know.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Sophie,
Thanks for your reply.
"Sophie Guo [MSFT]" wrote:
> The final release of this hotfix for SP4 has not been determined. If there
> is any update we will let you know.
The knowlege base article for 826906 says that the hotfix will be available
"shortly."
This bug is biting us hard. Can you give me a hint as to what "shortly"
means?
Thanks,
Jonathan|||Hello,
I appologize that we are unable to offer any further information on this
matter. Once the update is released, we will update you as soon as
possible and the article will be update.
I suggest that you unsintall SP4 and reinstall SP3 and the hotfix if the
issue is urgent. For more information about uninstalling SP4, you may refer
to the readme file of the SQL server 2000 SP4.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Do these guys even read this stuff?
Johnathan, how do you know whether or not this fix made it into the SP4
release?
As you know, SQL Server builds are cumulative. The fix you are referring to
is build 8.00.850. The cutoff build for the SP4 Beta was originally set at
8.00.972 and relabled 8.00.2026 to allow additional post-SP3 hotfixes not
included in SP4. The final release for SP4, build 8.00.2039, looks like it
included all fixes up through build 8.00.1007.
Also, here is the published list of fixes for the SP4 build:
A list of the bugs that are fixed in SQL Server 2000 Service Pack 4
http://support.microsoft.com/default.aspx?scid=kb;en-us;888799
If you need it, here is the list of post-SP3 hotfixes:
SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a
http://support.microsoft.com/?kbid=810185
Hope this helps.
Sincerely,
Anthony Thomas
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:1%23mFpMfYFHA.3336@.TK2MSFTNGXA01.phx.gbl...
Hello,
I appologize that we are unable to offer any further information on this
matter. Once the update is released, we will update you as soon as
possible and the article will be update.
I suggest that you unsintall SP4 and reinstall SP3 and the hotfix if the
issue is urgent. For more information about uninstalling SP4, you may refer
to the readme file of the SQL server 2000 SP4.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Anthony,
Thanks for your reply.
"Anthony Thomas" wrote:
> Johnathan, how do you know whether or not this fix made it into the SP4
> release?
I'm going by the text of article 826906, which says, in part, "Note This
hotfix is not included with Microsoft SQL Server 2000 Service Pack 4 (SP4).
If you apply this hotfix and then apply SP4, this hotfix will be overwritten.
A hotfix for SP4 will soon be available."
Regards,
Jonathan|||Yep, it sure does say that, but the Fixlist KB shows that it is included;
so, since the KB you are referencing is more recent (by about a week, at
most), I'd have to go with that. However, that is in direct contridiction
with how MS deploys cumulative builds.
The only thing I can conclude from this is that it had been included in the
Beta version but had been removed prior to public release.
So, your choices are to go ahead and deploy SP 4 and wait for the hotfix
they are working on to reinclude it, contact PSS to get the hot fix listed
in this KB, or apply a different, later post-SP3 hotfix that MUST contain
this fix, following MS cumulative build strategy.
The latest publicly available, post-SP3 hotfix is for build 8.00.878 and can
be downloaded here:
You must install the SQL Server 2000 update that KB article 831950 describes
to run BizTalk Server 2004
http://support.microsoft.com/?kbid=838166
For the english version:
http://download.microsoft.com/download/9/0/4/9046652b-2b9b-4d49-98c8-e74ba1849af5/sql2000-kb810185-8.00.0878-enu.exe
This one replaced the last publicly available, post-SP3 hotfix, build
8.00.859 because it had severe bugs in it.
Hope this helps.
Sincerely,
Anthony Thomas
"Jonathan Levine" <myfoo2@.nospam.nospam> wrote in message
news:9ADED83C-EDBE-4811-8881-622AA3C21103@.microsoft.com...
Anthony,
Thanks for your reply.
"Anthony Thomas" wrote:
> Johnathan, how do you know whether or not this fix made it into the SP4
> release?
I'm going by the text of article 826906, which says, in part, "Note This
hotfix is not included with Microsoft SQL Server 2000 Service Pack 4 (SP4).
If you apply this hotfix and then apply SP4, this hotfix will be
overwritten.
A hotfix for SP4 will soon be available."
Regards,
Jonathan|||"Sophie Guo [MSFT]" wrote:
> I appologize that we are unable to offer any further information on this
> matter. Once the update is released, we will update you as soon as
> possible and the article will be update.
Sophie,
It's now been a month since article 826906 was last updated, promising
that a "hotfix for SP4 will soon be available."
Is there any news on when it will be "soon?"
Regards,
Jonathan|||Hello,
The exact ship date is not known as it must await another package being
delivered. Thanks.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi, Sophie. Any news on this one? It's been months now...
Regards,
Jonathan
"Sophie Guo [MSFT]" wrote:
> Hello,
> The exact ship date is not known as it must await another package being
> delivered. Thanks.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>|||Hello,
I read the folloiwng information internally:
This hotfix is scheduled to be included with a post-Service Pack 4 hotfix
rollup package and with SQL Server 2000 Service Pack 5.
If the issue is urgent, please contact Customer Service and Support (CSS)
for immediate assistance. For more information on available CSS services,
please click here:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
NOTE: In special cases, charges that are ordinarily incurred for support
calls may be canceled if a Microsoft Support Professional determines that a
specific update will resolve your problem. The typical support costs will
apply to additional support questions and issues that do not qualify for
the specific update in question.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Sophie, thanks for your reply.
"Sophie Guo [MSFT]" wrote:
> This hotfix is scheduled to be included with a post-Service Pack 4 hotfix
> rollup package and with SQL Server 2000 Service Pack 5.
> If the issue is urgent, please contact Customer Service and Support (CSS)
> for immediate assistance. For more information on available CSS services,
> please click here:
I'm not sure what this means. Does it mean:
1. There's a hotfix I can get now?
Or
2. The fix is available but hasn't been packaged yet, and won't be
packaged unless enough people call and complain?
Or
3. The fix is not yet available?
Or
4. Something else?
Thanks,|||Hello,
The hotfix for SP4 is still unavailable now. However, if the issue is
urgent, CSS will investigate this issue at the urgent level and might
provide a hot fix for you. Thanks.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label described. Show all posts
Showing posts with label described. Show all posts
Friday, February 24, 2012
Hotfix fixed my SQL Server
I've applied "Hotfix 8.00.0859", which I downloaded from the Microsoft site,
and now I get the "Invalid cursor state" error described here
http://support.microsoft.com/?kbid=831997
The article says there is another hotfix that fixes what the previous hotfix
screwed up, and one should contact "Microsoft Product Support Services" to
get the new hotfix, and give a hyperlink to support where you can pay to
call MS, etc, which I don't really intend to do.
Anyone knows of a better way to get this new hotfix, have a link to it
maybe? I've downloaded the previous one, don't understand why this one is so
special.
Thanks.> give a hyperlink to support where you can pay to
> call MS, etc, which I don't really intend to do.
I suppose you've never done this before. If it's a bug in the product, and
they provide you with a fix, you are not charged for the call. In any
case...
> maybe? I've downloaded the previous one, don't understand why this one is
> so special.
Most hotfixes are not freely available because, as the article always
states, it is only intended to fix the specific problem for those sites that
are having the problem (e.g., not everyone and their brother). The reason
the hotfixes aren't handed out to everyone is because they are not fully
regression tested, and could possibly introduce other problems (e.g.
"Invalid Cursor State").
In your case, there is a newer hotfix that is publicly available. See the
end of http://www.aspfaq.com/2515
I would *STRONGLY* recommend, in the future, that you do not apply hotfixes
just because they are available to download from the Microsoft web site.
http://www.aspfaq.com/
(Reverse address to reply.)|||Aaron, thanks for the link, I am going to give the hotfix a shot.
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
Actually I've been programming with SQL Server for 10 years now and this was
my first hotfix ever, applied last Sunday after fighting a Report Server
install for about six hours, and someone that had the problem gave the
advice. In the end it was something else, but after six hours you don't ask
questions any more, I was ready for a total SQL Server re-install.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
>
is[vbcol=seagreen]
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||Hi Aaron,
The link you gave me to the hotfix fixed the problem, thanks.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
>
is[vbcol=seagreen]
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
and now I get the "Invalid cursor state" error described here
http://support.microsoft.com/?kbid=831997
The article says there is another hotfix that fixes what the previous hotfix
screwed up, and one should contact "Microsoft Product Support Services" to
get the new hotfix, and give a hyperlink to support where you can pay to
call MS, etc, which I don't really intend to do.
Anyone knows of a better way to get this new hotfix, have a link to it
maybe? I've downloaded the previous one, don't understand why this one is so
special.
Thanks.> give a hyperlink to support where you can pay to
> call MS, etc, which I don't really intend to do.
I suppose you've never done this before. If it's a bug in the product, and
they provide you with a fix, you are not charged for the call. In any
case...
> maybe? I've downloaded the previous one, don't understand why this one is
> so special.
Most hotfixes are not freely available because, as the article always
states, it is only intended to fix the specific problem for those sites that
are having the problem (e.g., not everyone and their brother). The reason
the hotfixes aren't handed out to everyone is because they are not fully
regression tested, and could possibly introduce other problems (e.g.
"Invalid Cursor State").
In your case, there is a newer hotfix that is publicly available. See the
end of http://www.aspfaq.com/2515
I would *STRONGLY* recommend, in the future, that you do not apply hotfixes
just because they are available to download from the Microsoft web site.
http://www.aspfaq.com/
(Reverse address to reply.)|||Aaron, thanks for the link, I am going to give the hotfix a shot.
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
Actually I've been programming with SQL Server for 10 years now and this was
my first hotfix ever, applied last Sunday after fighting a Report Server
install for about six hours, and someone that had the problem gave the
advice. In the end it was something else, but after six hours you don't ask
questions any more, I was ready for a total SQL Server re-install.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
>
is[vbcol=seagreen]
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||Hi Aaron,
The link you gave me to the hotfix fixed the problem, thanks.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
>
is[vbcol=seagreen]
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
Hotfix fixed my SQL Server
I've applied "Hotfix 8.00.0859", which I downloaded from the Microsoft site,
and now I get the "Invalid cursor state" error described here
http://support.microsoft.com/?kbid=831997
The article says there is another hotfix that fixes what the previous hotfix
screwed up, and one should contact "Microsoft Product Support Services" to
get the new hotfix, and give a hyperlink to support where you can pay to
call MS, etc, which I don't really intend to do.
Anyone knows of a better way to get this new hotfix, have a link to it
maybe? I've downloaded the previous one, don't understand why this one is so
special.
Thanks.
> give a hyperlink to support where you can pay to
> call MS, etc, which I don't really intend to do.
I suppose you've never done this before. If it's a bug in the product, and
they provide you with a fix, you are not charged for the call. In any
case...
> maybe? I've downloaded the previous one, don't understand why this one is
> so special.
Most hotfixes are not freely available because, as the article always
states, it is only intended to fix the specific problem for those sites that
are having the problem (e.g., not everyone and their brother). The reason
the hotfixes aren't handed out to everyone is because they are not fully
regression tested, and could possibly introduce other problems (e.g.
"Invalid Cursor State").
In your case, there is a newer hotfix that is publicly available. See the
end of http://www.aspfaq.com/2515
I would *STRONGLY* recommend, in the future, that you do not apply hotfixes
just because they are available to download from the Microsoft web site.
http://www.aspfaq.com/
(Reverse address to reply.)
|||Aaron, thanks for the link, I am going to give the hotfix a shot.
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
Actually I've been programming with SQL Server for 10 years now and this was
my first hotfix ever, applied last Sunday after fighting a Report Server
install for about six hours, and someone that had the problem gave the
advice. In the end it was something else, but after six hours you don't ask
questions any more, I was ready for a total SQL Server re-install.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and[vbcol=seagreen]
> they provide you with a fix, you are not charged for the call. In any
> case...
is
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||Hi Aaron,
The link you gave me to the hotfix fixed the problem, thanks.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and[vbcol=seagreen]
> they provide you with a fix, you are not charged for the call. In any
> case...
is
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
and now I get the "Invalid cursor state" error described here
http://support.microsoft.com/?kbid=831997
The article says there is another hotfix that fixes what the previous hotfix
screwed up, and one should contact "Microsoft Product Support Services" to
get the new hotfix, and give a hyperlink to support where you can pay to
call MS, etc, which I don't really intend to do.
Anyone knows of a better way to get this new hotfix, have a link to it
maybe? I've downloaded the previous one, don't understand why this one is so
special.
Thanks.
> give a hyperlink to support where you can pay to
> call MS, etc, which I don't really intend to do.
I suppose you've never done this before. If it's a bug in the product, and
they provide you with a fix, you are not charged for the call. In any
case...
> maybe? I've downloaded the previous one, don't understand why this one is
> so special.
Most hotfixes are not freely available because, as the article always
states, it is only intended to fix the specific problem for those sites that
are having the problem (e.g., not everyone and their brother). The reason
the hotfixes aren't handed out to everyone is because they are not fully
regression tested, and could possibly introduce other problems (e.g.
"Invalid Cursor State").
In your case, there is a newer hotfix that is publicly available. See the
end of http://www.aspfaq.com/2515
I would *STRONGLY* recommend, in the future, that you do not apply hotfixes
just because they are available to download from the Microsoft web site.
http://www.aspfaq.com/
(Reverse address to reply.)
|||Aaron, thanks for the link, I am going to give the hotfix a shot.
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
Actually I've been programming with SQL Server for 10 years now and this was
my first hotfix ever, applied last Sunday after fighting a Report Server
install for about six hours, and someone that had the problem gave the
advice. In the end it was something else, but after six hours you don't ask
questions any more, I was ready for a total SQL Server re-install.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and[vbcol=seagreen]
> they provide you with a fix, you are not charged for the call. In any
> case...
is
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||Hi Aaron,
The link you gave me to the hotfix fixed the problem, thanks.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> I suppose you've never done this before. If it's a bug in the product,
and[vbcol=seagreen]
> they provide you with a fix, you are not charged for the call. In any
> case...
is
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
Hotfix fixed my SQL Server
I've applied "Hotfix 8.00.0859", which I downloaded from the Microsoft site,
and now I get the "Invalid cursor state" error described here
http://support.microsoft.com/?kbid=831997
The article says there is another hotfix that fixes what the previous hotfix
screwed up, and one should contact "Microsoft Product Support Services" to
get the new hotfix, and give a hyperlink to support where you can pay to
call MS, etc, which I don't really intend to do.
Anyone knows of a better way to get this new hotfix, have a link to it
maybe? I've downloaded the previous one, don't understand why this one is so
special.
Thanks.> give a hyperlink to support where you can pay to
> call MS, etc, which I don't really intend to do.
I suppose you've never done this before. If it's a bug in the product, and
they provide you with a fix, you are not charged for the call. In any
case...
> maybe? I've downloaded the previous one, don't understand why this one is
> so special.
Most hotfixes are not freely available because, as the article always
states, it is only intended to fix the specific problem for those sites that
are having the problem (e.g., not everyone and their brother). The reason
the hotfixes aren't handed out to everyone is because they are not fully
regression tested, and could possibly introduce other problems (e.g.
"Invalid Cursor State").
In your case, there is a newer hotfix that is publicly available. See the
end of http://www.aspfaq.com/2515
I would *STRONGLY* recommend, in the future, that you do not apply hotfixes
just because they are available to download from the Microsoft web site.
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Aaron, thanks for the link, I am going to give the hotfix a shot.
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
Actually I've been programming with SQL Server for 10 years now and this was
my first hotfix ever, applied last Sunday after fighting a Report Server
install for about six hours, and someone that had the problem gave the
advice. In the end it was something else, but after six hours you don't ask
questions any more, I was ready for a total SQL Server re-install.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> > give a hyperlink to support where you can pay to
> > call MS, etc, which I don't really intend to do.
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
> > maybe? I've downloaded the previous one, don't understand why this one
is
> > so special.
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||Hi Aaron,
The link you gave me to the hotfix fixed the problem, thanks.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> > give a hyperlink to support where you can pay to
> > call MS, etc, which I don't really intend to do.
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
> > maybe? I've downloaded the previous one, don't understand why this one
is
> > so special.
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||I have the same problem. Did you get a fix?
Thanks!
~ Troy
>--Original Message--
>I've applied "Hotfix 8.00.0859", which I downloaded from
the Microsoft site,
>and now I get the "Invalid cursor state" error described
here
>http://support.microsoft.com/?kbid=831997
>The article says there is another hotfix that fixes what
the previous hotfix
>screwed up, and one should contact "Microsoft Product
Support Services" to
>get the new hotfix, and give a hyperlink to support where
you can pay to
>call MS, etc, which I don't really intend to do.
>Anyone knows of a better way to get this new hotfix, have
a link to it
>maybe? I've downloaded the previous one, don't understand
why this one is so
>special.
>Thanks.
>
>.
>|||> I have the same problem. Did you get a fix?
Did you read the rest of the thread you replied to?|||The direct link to the fix that fixed it for me (thanks to Aaron) is
http://support.microsoft.com/?kbid=838166
"Troy Anderson" <tanderso@.sonoma-county.org> wrote in message
news:322801c46385$3df4f380$3a01280a@.phx.gbl...
> I have the same problem. Did you get a fix?
> Thanks!
> ~ Troy
> >--Original Message--
> >I've applied "Hotfix 8.00.0859", which I downloaded from
> the Microsoft site,
> >and now I get the "Invalid cursor state" error described
> here
> >http://support.microsoft.com/?kbid=831997
> >
> >The article says there is another hotfix that fixes what
> the previous hotfix
> >screwed up, and one should contact "Microsoft Product
> Support Services" to
> >get the new hotfix, and give a hyperlink to support where
> you can pay to
> >call MS, etc, which I don't really intend to do.
> >Anyone knows of a better way to get this new hotfix, have
> a link to it
> >maybe? I've downloaded the previous one, don't understand
> why this one is so
> >special.
> >
> >Thanks.
> >
> >
> >.
> >
and now I get the "Invalid cursor state" error described here
http://support.microsoft.com/?kbid=831997
The article says there is another hotfix that fixes what the previous hotfix
screwed up, and one should contact "Microsoft Product Support Services" to
get the new hotfix, and give a hyperlink to support where you can pay to
call MS, etc, which I don't really intend to do.
Anyone knows of a better way to get this new hotfix, have a link to it
maybe? I've downloaded the previous one, don't understand why this one is so
special.
Thanks.> give a hyperlink to support where you can pay to
> call MS, etc, which I don't really intend to do.
I suppose you've never done this before. If it's a bug in the product, and
they provide you with a fix, you are not charged for the call. In any
case...
> maybe? I've downloaded the previous one, don't understand why this one is
> so special.
Most hotfixes are not freely available because, as the article always
states, it is only intended to fix the specific problem for those sites that
are having the problem (e.g., not everyone and their brother). The reason
the hotfixes aren't handed out to everyone is because they are not fully
regression tested, and could possibly introduce other problems (e.g.
"Invalid Cursor State").
In your case, there is a newer hotfix that is publicly available. See the
end of http://www.aspfaq.com/2515
I would *STRONGLY* recommend, in the future, that you do not apply hotfixes
just because they are available to download from the Microsoft web site.
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Aaron, thanks for the link, I am going to give the hotfix a shot.
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
Actually I've been programming with SQL Server for 10 years now and this was
my first hotfix ever, applied last Sunday after fighting a Report Server
install for about six hours, and someone that had the problem gave the
advice. In the end it was something else, but after six hours you don't ask
questions any more, I was ready for a total SQL Server re-install.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> > give a hyperlink to support where you can pay to
> > call MS, etc, which I don't really intend to do.
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
> > maybe? I've downloaded the previous one, don't understand why this one
is
> > so special.
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||Hi Aaron,
The link you gave me to the hotfix fixed the problem, thanks.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:unm3O0wXEHA.3156@.TK2MSFTNGP12.phx.gbl...
> > give a hyperlink to support where you can pay to
> > call MS, etc, which I don't really intend to do.
> I suppose you've never done this before. If it's a bug in the product,
and
> they provide you with a fix, you are not charged for the call. In any
> case...
> > maybe? I've downloaded the previous one, don't understand why this one
is
> > so special.
> Most hotfixes are not freely available because, as the article always
> states, it is only intended to fix the specific problem for those sites
that
> are having the problem (e.g., not everyone and their brother). The reason
> the hotfixes aren't handed out to everyone is because they are not fully
> regression tested, and could possibly introduce other problems (e.g.
> "Invalid Cursor State").
> In your case, there is a newer hotfix that is publicly available. See the
> end of http://www.aspfaq.com/2515
> I would *STRONGLY* recommend, in the future, that you do not apply
hotfixes
> just because they are available to download from the Microsoft web site.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||I have the same problem. Did you get a fix?
Thanks!
~ Troy
>--Original Message--
>I've applied "Hotfix 8.00.0859", which I downloaded from
the Microsoft site,
>and now I get the "Invalid cursor state" error described
here
>http://support.microsoft.com/?kbid=831997
>The article says there is another hotfix that fixes what
the previous hotfix
>screwed up, and one should contact "Microsoft Product
Support Services" to
>get the new hotfix, and give a hyperlink to support where
you can pay to
>call MS, etc, which I don't really intend to do.
>Anyone knows of a better way to get this new hotfix, have
a link to it
>maybe? I've downloaded the previous one, don't understand
why this one is so
>special.
>Thanks.
>
>.
>|||> I have the same problem. Did you get a fix?
Did you read the rest of the thread you replied to?|||The direct link to the fix that fixed it for me (thanks to Aaron) is
http://support.microsoft.com/?kbid=838166
"Troy Anderson" <tanderso@.sonoma-county.org> wrote in message
news:322801c46385$3df4f380$3a01280a@.phx.gbl...
> I have the same problem. Did you get a fix?
> Thanks!
> ~ Troy
> >--Original Message--
> >I've applied "Hotfix 8.00.0859", which I downloaded from
> the Microsoft site,
> >and now I get the "Invalid cursor state" error described
> here
> >http://support.microsoft.com/?kbid=831997
> >
> >The article says there is another hotfix that fixes what
> the previous hotfix
> >screwed up, and one should contact "Microsoft Product
> Support Services" to
> >get the new hotfix, and give a hyperlink to support where
> you can pay to
> >call MS, etc, which I don't really intend to do.
> >Anyone knows of a better way to get this new hotfix, have
> a link to it
> >maybe? I've downloaded the previous one, don't understand
> why this one is so
> >special.
> >
> >Thanks.
> >
> >
> >.
> >
Hotfix 934459.
Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
Now I have the error described in Fix 934459 (The Check Database Integrity
task and the Execute T-SQL Statement task in a maintenance plan may lose
database context in certain circumstances ), but my build 9.0.3054 doesn't
seem to be in the affected ones..
Should I install the hotfix? Which one?
This are the two available
If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
http://support.microsoft.com/kb/934459/
If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
http://support.microsoft.com/kb/934458/
Thanks.
You should get 3200 or, better yet, 3215 instead.
9.0.3200:
http://support.microsoft.com/kb/941450
9.0.3215:
http://support.microsoft.com/kb/943656
"averied" <averied@.discussions.microsoft.com> wrote in message
news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
> Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
> Now I have the error described in Fix 934459 (The Check Database Integrity
> task and the Execute T-SQL Statement task in a maintenance plan may lose
> database context in certain circumstances ), but my build 9.0.3054 doesn't
> seem to be in the affected ones..
> Should I install the hotfix? Which one?
> This are the two available
> If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
> http://support.microsoft.com/kb/934459/
> If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
> http://support.microsoft.com/kb/934458/
>
> Thanks.
>
|||I installed the Cumulative update package 4 for SQL Server 2005 Service Pack
2 and rebooted my machine, yet my version still shows 9.00.3042. The
installation appeared to function properly w/ no errors. How can I tell that
this hot fix did indeed install?
Cordially,
Mark Boettcher
PS, I have just now requested the hotfix for 3215 and should get it tomorrow.
"Aaron Bertrand [SQL Server MVP]" wrote:
> You should get 3200 or, better yet, 3215 instead.
> 9.0.3200:
> http://support.microsoft.com/kb/941450
> 9.0.3215:
> http://support.microsoft.com/kb/943656
>
>
> "averied" <averied@.discussions.microsoft.com> wrote in message
> news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
>
>
|||>I installed the Cumulative update package 4 for SQL Server 2005 Service
>Pack
> 2 and rebooted my machine, yet my version still shows 9.00.3042.
Where/how are you checking "my version"?
A
|||In server management studio, I right-clicked on registered server and found
it under properties. If not there, how should I display the sql version?
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> Where/how are you checking "my version"?
> A
>
|||That is the version for the tools (Management Studio). Open a query window
connected to the server you updated, and then run:
SELECT @.@.VERSION;
"Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...[vbcol=seagreen]
> In server management studio, I right-clicked on registered server and
> found
> it under properties. If not there, how should I display the sql version?
> Mark
> "Aaron Bertrand [SQL Server MVP]" wrote:
|||Since I installed Cumulative update package 4, I requested, received, and
installed Cumulative update package 5. Using the Select @.@.Version command
returns 9.00.3215 now. I assume Cumulative update package 5 includes the
changes in Cumulative update package 4 - correct? After I installed package
4, I did do a select @.@.version and received 9.00.3042 which is why I
questioned whether the package really did install.
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> That is the version for the tools (Management Studio). Open a query window
> connected to the server you updated, and then run:
> SELECT @.@.VERSION;
>
> "Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
> news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...
>
|||> returns 9.00.3215 now. I assume Cumulative update package 5 includes the
> changes in Cumulative update package 4 - correct?
Yes, each cumulative update page states that cumulative updates are
cumulative -- that's why they're named as such. :-)
> After I installed package
> 4, I did do a select @.@.version and received 9.00.3042
Then the install didn't succeed, or you ran SELECT @.@.VERSION against the
wrong server.
A
Now I have the error described in Fix 934459 (The Check Database Integrity
task and the Execute T-SQL Statement task in a maintenance plan may lose
database context in certain circumstances ), but my build 9.0.3054 doesn't
seem to be in the affected ones..
Should I install the hotfix? Which one?
This are the two available
If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
http://support.microsoft.com/kb/934459/
If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
http://support.microsoft.com/kb/934458/
Thanks.
You should get 3200 or, better yet, 3215 instead.
9.0.3200:
http://support.microsoft.com/kb/941450
9.0.3215:
http://support.microsoft.com/kb/943656
"averied" <averied@.discussions.microsoft.com> wrote in message
news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
> Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
> Now I have the error described in Fix 934459 (The Check Database Integrity
> task and the Execute T-SQL Statement task in a maintenance plan may lose
> database context in certain circumstances ), but my build 9.0.3054 doesn't
> seem to be in the affected ones..
> Should I install the hotfix? Which one?
> This are the two available
> If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
> http://support.microsoft.com/kb/934459/
> If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
> http://support.microsoft.com/kb/934458/
>
> Thanks.
>
|||I installed the Cumulative update package 4 for SQL Server 2005 Service Pack
2 and rebooted my machine, yet my version still shows 9.00.3042. The
installation appeared to function properly w/ no errors. How can I tell that
this hot fix did indeed install?
Cordially,
Mark Boettcher
PS, I have just now requested the hotfix for 3215 and should get it tomorrow.
"Aaron Bertrand [SQL Server MVP]" wrote:
> You should get 3200 or, better yet, 3215 instead.
> 9.0.3200:
> http://support.microsoft.com/kb/941450
> 9.0.3215:
> http://support.microsoft.com/kb/943656
>
>
> "averied" <averied@.discussions.microsoft.com> wrote in message
> news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
>
>
|||>I installed the Cumulative update package 4 for SQL Server 2005 Service
>Pack
> 2 and rebooted my machine, yet my version still shows 9.00.3042.
Where/how are you checking "my version"?
A
|||In server management studio, I right-clicked on registered server and found
it under properties. If not there, how should I display the sql version?
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> Where/how are you checking "my version"?
> A
>
|||That is the version for the tools (Management Studio). Open a query window
connected to the server you updated, and then run:
SELECT @.@.VERSION;
"Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...[vbcol=seagreen]
> In server management studio, I right-clicked on registered server and
> found
> it under properties. If not there, how should I display the sql version?
> Mark
> "Aaron Bertrand [SQL Server MVP]" wrote:
|||Since I installed Cumulative update package 4, I requested, received, and
installed Cumulative update package 5. Using the Select @.@.Version command
returns 9.00.3215 now. I assume Cumulative update package 5 includes the
changes in Cumulative update package 4 - correct? After I installed package
4, I did do a select @.@.version and received 9.00.3042 which is why I
questioned whether the package really did install.
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> That is the version for the tools (Management Studio). Open a query window
> connected to the server you updated, and then run:
> SELECT @.@.VERSION;
>
> "Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
> news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...
>
|||> returns 9.00.3215 now. I assume Cumulative update package 5 includes the
> changes in Cumulative update package 4 - correct?
Yes, each cumulative update page states that cumulative updates are
cumulative -- that's why they're named as such. :-)
> After I installed package
> 4, I did do a select @.@.version and received 9.00.3042
Then the install didn't succeed, or you ran SELECT @.@.VERSION against the
wrong server.
A
Hotfix 934459.
Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
Now I have the error described in Fix 934459 (The Check Database Integrity
task and the Execute T-SQL Statement task in a maintenance plan may lose
database context in certain circumstances ), but my build 9.0.3054 doesn't
seem to be in the affected ones..
Should I install the hotfix' Which one'
This are the two available
If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
http://support.microsoft.com/kb/934459/
If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
http://support.microsoft.com/kb/934458/
Thanks.You should get 3200 or, better yet, 3215 instead.
9.0.3200:
http://support.microsoft.com/kb/941450
9.0.3215:
http://support.microsoft.com/kb/943656
"averied" <averied@.discussions.microsoft.com> wrote in message
news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
> Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
> Now I have the error described in Fix 934459 (The Check Database Integrity
> task and the Execute T-SQL Statement task in a maintenance plan may lose
> database context in certain circumstances ), but my build 9.0.3054 doesn't
> seem to be in the affected ones..
> Should I install the hotfix' Which one'
> This are the two available
> If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
> http://support.microsoft.com/kb/934459/
> If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
> http://support.microsoft.com/kb/934458/
>
> Thanks.
>|||I installed the Cumulative update package 4 for SQL Server 2005 Service Pack
2 and rebooted my machine, yet my version still shows 9.00.3042. The
installation appeared to function properly w/ no errors. How can I tell that
this hot fix did indeed install?
Cordially,
Mark Boettcher
PS, I have just now requested the hotfix for 3215 and should get it tomorrow.
"Aaron Bertrand [SQL Server MVP]" wrote:
> You should get 3200 or, better yet, 3215 instead.
> 9.0.3200:
> http://support.microsoft.com/kb/941450
> 9.0.3215:
> http://support.microsoft.com/kb/943656
>
>
> "averied" <averied@.discussions.microsoft.com> wrote in message
> news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
> > Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
> >
> > Now I have the error described in Fix 934459 (The Check Database Integrity
> > task and the Execute T-SQL Statement task in a maintenance plan may lose
> > database context in certain circumstances ), but my build 9.0.3054 doesn't
> > seem to be in the affected ones..
> >
> > Should I install the hotfix' Which one'
> >
> > This are the two available
> >
> > If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
> > http://support.microsoft.com/kb/934459/
> >
> > If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
> > http://support.microsoft.com/kb/934458/
> >
> >
> > Thanks.
> >
>
>|||>I installed the Cumulative update package 4 for SQL Server 2005 Service
>Pack
> 2 and rebooted my machine, yet my version still shows 9.00.3042.
Where/how are you checking "my version"?
A|||In server management studio, I right-clicked on registered server and found
it under properties. If not there, how should I display the sql version?
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> >I installed the Cumulative update package 4 for SQL Server 2005 Service
> >Pack
> > 2 and rebooted my machine, yet my version still shows 9.00.3042.
> Where/how are you checking "my version"?
> A
>|||That is the version for the tools (Management Studio). Open a query window
connected to the server you updated, and then run:
SELECT @.@.VERSION;
"Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...
> In server management studio, I right-clicked on registered server and
> found
> it under properties. If not there, how should I display the sql version?
> Mark
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> >I installed the Cumulative update package 4 for SQL Server 2005 Service
>> >Pack
>> > 2 and rebooted my machine, yet my version still shows 9.00.3042.
>> Where/how are you checking "my version"?
>> A|||Since I installed Cumulative update package 4, I requested, received, and
installed Cumulative update package 5. Using the Select @.@.Version command
returns 9.00.3215 now. I assume Cumulative update package 5 includes the
changes in Cumulative update package 4 - correct? After I installed package
4, I did do a select @.@.version and received 9.00.3042 which is why I
questioned whether the package really did install.
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> That is the version for the tools (Management Studio). Open a query window
> connected to the server you updated, and then run:
> SELECT @.@.VERSION;
>
> "Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
> news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...
> > In server management studio, I right-clicked on registered server and
> > found
> > it under properties. If not there, how should I display the sql version?
> >
> > Mark
> >
> > "Aaron Bertrand [SQL Server MVP]" wrote:
> >
> >> >I installed the Cumulative update package 4 for SQL Server 2005 Service
> >> >Pack
> >> > 2 and rebooted my machine, yet my version still shows 9.00.3042.
> >>
> >> Where/how are you checking "my version"?
> >>
> >> A
> >>
>|||> returns 9.00.3215 now. I assume Cumulative update package 5 includes the
> changes in Cumulative update package 4 - correct?
Yes, each cumulative update page states that cumulative updates are
cumulative -- that's why they're named as such. :-)
> After I installed package
> 4, I did do a select @.@.version and received 9.00.3042
Then the install didn't succeed, or you ran SELECT @.@.VERSION against the
wrong server.
A
Now I have the error described in Fix 934459 (The Check Database Integrity
task and the Execute T-SQL Statement task in a maintenance plan may lose
database context in certain circumstances ), but my build 9.0.3054 doesn't
seem to be in the affected ones..
Should I install the hotfix' Which one'
This are the two available
If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
http://support.microsoft.com/kb/934459/
If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
http://support.microsoft.com/kb/934458/
Thanks.You should get 3200 or, better yet, 3215 instead.
9.0.3200:
http://support.microsoft.com/kb/941450
9.0.3215:
http://support.microsoft.com/kb/943656
"averied" <averied@.discussions.microsoft.com> wrote in message
news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
> Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
> Now I have the error described in Fix 934459 (The Check Database Integrity
> task and the Execute T-SQL Statement task in a maintenance plan may lose
> database context in certain circumstances ), but my build 9.0.3054 doesn't
> seem to be in the affected ones..
> Should I install the hotfix' Which one'
> This are the two available
> If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
> http://support.microsoft.com/kb/934459/
> If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
> http://support.microsoft.com/kb/934458/
>
> Thanks.
>|||I installed the Cumulative update package 4 for SQL Server 2005 Service Pack
2 and rebooted my machine, yet my version still shows 9.00.3042. The
installation appeared to function properly w/ no errors. How can I tell that
this hot fix did indeed install?
Cordially,
Mark Boettcher
PS, I have just now requested the hotfix for 3215 and should get it tomorrow.
"Aaron Bertrand [SQL Server MVP]" wrote:
> You should get 3200 or, better yet, 3215 instead.
> 9.0.3200:
> http://support.microsoft.com/kb/941450
> 9.0.3215:
> http://support.microsoft.com/kb/943656
>
>
> "averied" <averied@.discussions.microsoft.com> wrote in message
> news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
> > Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
> >
> > Now I have the error described in Fix 934459 (The Check Database Integrity
> > task and the Execute T-SQL Statement task in a maintenance plan may lose
> > database context in certain circumstances ), but my build 9.0.3054 doesn't
> > seem to be in the affected ones..
> >
> > Should I install the hotfix' Which one'
> >
> > This are the two available
> >
> > If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
> > http://support.microsoft.com/kb/934459/
> >
> > If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
> > http://support.microsoft.com/kb/934458/
> >
> >
> > Thanks.
> >
>
>|||>I installed the Cumulative update package 4 for SQL Server 2005 Service
>Pack
> 2 and rebooted my machine, yet my version still shows 9.00.3042.
Where/how are you checking "my version"?
A|||In server management studio, I right-clicked on registered server and found
it under properties. If not there, how should I display the sql version?
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> >I installed the Cumulative update package 4 for SQL Server 2005 Service
> >Pack
> > 2 and rebooted my machine, yet my version still shows 9.00.3042.
> Where/how are you checking "my version"?
> A
>|||That is the version for the tools (Management Studio). Open a query window
connected to the server you updated, and then run:
SELECT @.@.VERSION;
"Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...
> In server management studio, I right-clicked on registered server and
> found
> it under properties. If not there, how should I display the sql version?
> Mark
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> >I installed the Cumulative update package 4 for SQL Server 2005 Service
>> >Pack
>> > 2 and rebooted my machine, yet my version still shows 9.00.3042.
>> Where/how are you checking "my version"?
>> A|||Since I installed Cumulative update package 4, I requested, received, and
installed Cumulative update package 5. Using the Select @.@.Version command
returns 9.00.3215 now. I assume Cumulative update package 5 includes the
changes in Cumulative update package 4 - correct? After I installed package
4, I did do a select @.@.version and received 9.00.3042 which is why I
questioned whether the package really did install.
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> That is the version for the tools (Management Studio). Open a query window
> connected to the server you updated, and then run:
> SELECT @.@.VERSION;
>
> "Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
> news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...
> > In server management studio, I right-clicked on registered server and
> > found
> > it under properties. If not there, how should I display the sql version?
> >
> > Mark
> >
> > "Aaron Bertrand [SQL Server MVP]" wrote:
> >
> >> >I installed the Cumulative update package 4 for SQL Server 2005 Service
> >> >Pack
> >> > 2 and rebooted my machine, yet my version still shows 9.00.3042.
> >>
> >> Where/how are you checking "my version"?
> >>
> >> A
> >>
>|||> returns 9.00.3215 now. I assume Cumulative update package 5 includes the
> changes in Cumulative update package 4 - correct?
Yes, each cumulative update page states that cumulative updates are
cumulative -- that's why they're named as such. :-)
> After I installed package
> 4, I did do a select @.@.version and received 9.00.3042
Then the install didn't succeed, or you ran SELECT @.@.VERSION against the
wrong server.
A
Sunday, February 19, 2012
Hot Fix Prerequisites and Need with Service Packs
We are looking at the possible deployment of the SQL 2005 hot fix
described in http://support.microsoft.com/kb/916002#appliesto to
resolve connection issues with .net to SQL. However, we are unable to
determine if this hot fix has any prerequisites (such as sp1), or if
it fixed in sp1 or even in sp2. I have searched extensively online,
and I do not see this as fixed in any service pack documents (although
the lists are seldom complete), and the prerequisites are missing in
the KB article.
Any help would be appreciated.
TerryIt's not a SQL Server hotfix:
APPLIES TO
. Microsoft ADO.NET 2.0
So in theory, you could be running RTM SQL 2005 and this would work after
applying the fix.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Terry" <tduffy@.calamos.com> wrote in message
news:1170253010.111201.95670@.p10g2000cwp.googlegroups.com...
> We are looking at the possible deployment of the SQL 2005 hot fix
> described in http://support.microsoft.com/kb/916002#appliesto to
> resolve connection issues with .net to SQL. However, we are unable to
> determine if this hot fix has any prerequisites (such as sp1), or if
> it fixed in sp1 or even in sp2. I have searched extensively online,
> and I do not see this as fixed in any service pack documents (although
> the lists are seldom complete), and the prerequisites are missing in
> the KB article.
> Any help would be appreciated.
> Terry
>|||On Jan 31, 9:47 am, "Kevin3NF" <k...@.SPAMTRAP.3nf-inc.com> wrote:
> It's not a SQL Server hotfix:
> APPLIES TO
> . Microsoft ADO.NET 2.0
> So in theory, you could be running RTM SQL 2005 and this would work after
> applying the fix.
> --
> Kevin Hill
> 3NF Consultinghttp://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:http://kevin3nf.blogspot.com
> "Terry" <tdu...@.calamos.com> wrote in message
> news:1170253010.111201.95670@.p10g2000cwp.googlegroups.com...
>
> > We are looking at the possible deployment of the SQL 2005 hot fix
> > described inhttp://support.microsoft.com/kb/916002#appliestoto
> > resolve connection issues with .net to SQL. However, we are unable to
> > determine if this hot fix has any prerequisites (such as sp1), or if
> > it fixed in sp1 or even in sp2. I have searched extensively online,
> > and I do not see this as fixed in any service pack documents (although
> > the lists are seldom complete), and the prerequisites are missing in
> > the KB article.
> > Any help would be appreciated.
> > Terry- Hide quoted text -
> - Show quoted text -
The KB Article mentions. BUG #: 483 (SQL Hotfix). What makes you say
this is not a SQL hotfix?
Terry|||The "applies to" is the defining term here, not the (SQL Hotfix) part...that
simply means the portion of ADO that is being fixed.
SQL Hotfix KBs have a list of the files that are being replaced, this KB
does not.
I tried to install it on my box and was told I did not have the product that
it applied to, but I do have the correct versions of SQL Server on my test
box.
Hope that helps :)
You can always call PSS and get a free incident opened and ask the same
question...just give them the KB article number when you call,
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
> The KB Article mentions. BUG #: 483 (SQL Hotfix). What makes you say
> this is not a SQL hotfix?
> Terry
>|||On Feb 1, 12:40 pm, "Kevin3NF" <k...@.SPAMTRAP.3nf-inc.com> wrote:
> The "applies to" is the defining term here, not the (SQL Hotfix) part...that
> simply means the portion of ADO that is being fixed.
> SQL Hotfix KBs have a list of the files that are being replaced, this KB
> does not.
> I tried to install it on my box and was told I did not have the product that
> it applied to, but I do have the correct versions of SQL Server on my test
> box.
> Hope that helps :)
> You can always call PSS and get a free incident opened and ask the same
> question...just give them the KB article number when you call,
> --
> Kevin Hill
> 3NF Consultinghttp://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:http://kevin3nf.blogspot.com
>
> > The KB Article mentions. BUG #: 483 (SQL Hotfix). What makes you say
> > this is not a SQL hotfix?
> > Terry- Hide quoted text -
> - Show quoted text -
Thank you Kevin. Your efforts and responses are greatly appreciated.
Terry
described in http://support.microsoft.com/kb/916002#appliesto to
resolve connection issues with .net to SQL. However, we are unable to
determine if this hot fix has any prerequisites (such as sp1), or if
it fixed in sp1 or even in sp2. I have searched extensively online,
and I do not see this as fixed in any service pack documents (although
the lists are seldom complete), and the prerequisites are missing in
the KB article.
Any help would be appreciated.
TerryIt's not a SQL Server hotfix:
APPLIES TO
. Microsoft ADO.NET 2.0
So in theory, you could be running RTM SQL 2005 and this would work after
applying the fix.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Terry" <tduffy@.calamos.com> wrote in message
news:1170253010.111201.95670@.p10g2000cwp.googlegroups.com...
> We are looking at the possible deployment of the SQL 2005 hot fix
> described in http://support.microsoft.com/kb/916002#appliesto to
> resolve connection issues with .net to SQL. However, we are unable to
> determine if this hot fix has any prerequisites (such as sp1), or if
> it fixed in sp1 or even in sp2. I have searched extensively online,
> and I do not see this as fixed in any service pack documents (although
> the lists are seldom complete), and the prerequisites are missing in
> the KB article.
> Any help would be appreciated.
> Terry
>|||On Jan 31, 9:47 am, "Kevin3NF" <k...@.SPAMTRAP.3nf-inc.com> wrote:
> It's not a SQL Server hotfix:
> APPLIES TO
> . Microsoft ADO.NET 2.0
> So in theory, you could be running RTM SQL 2005 and this would work after
> applying the fix.
> --
> Kevin Hill
> 3NF Consultinghttp://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:http://kevin3nf.blogspot.com
> "Terry" <tdu...@.calamos.com> wrote in message
> news:1170253010.111201.95670@.p10g2000cwp.googlegroups.com...
>
> > We are looking at the possible deployment of the SQL 2005 hot fix
> > described inhttp://support.microsoft.com/kb/916002#appliestoto
> > resolve connection issues with .net to SQL. However, we are unable to
> > determine if this hot fix has any prerequisites (such as sp1), or if
> > it fixed in sp1 or even in sp2. I have searched extensively online,
> > and I do not see this as fixed in any service pack documents (although
> > the lists are seldom complete), and the prerequisites are missing in
> > the KB article.
> > Any help would be appreciated.
> > Terry- Hide quoted text -
> - Show quoted text -
The KB Article mentions. BUG #: 483 (SQL Hotfix). What makes you say
this is not a SQL hotfix?
Terry|||The "applies to" is the defining term here, not the (SQL Hotfix) part...that
simply means the portion of ADO that is being fixed.
SQL Hotfix KBs have a list of the files that are being replaced, this KB
does not.
I tried to install it on my box and was told I did not have the product that
it applied to, but I do have the correct versions of SQL Server on my test
box.
Hope that helps :)
You can always call PSS and get a free incident opened and ask the same
question...just give them the KB article number when you call,
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
> The KB Article mentions. BUG #: 483 (SQL Hotfix). What makes you say
> this is not a SQL hotfix?
> Terry
>|||On Feb 1, 12:40 pm, "Kevin3NF" <k...@.SPAMTRAP.3nf-inc.com> wrote:
> The "applies to" is the defining term here, not the (SQL Hotfix) part...that
> simply means the portion of ADO that is being fixed.
> SQL Hotfix KBs have a list of the files that are being replaced, this KB
> does not.
> I tried to install it on my box and was told I did not have the product that
> it applied to, but I do have the correct versions of SQL Server on my test
> box.
> Hope that helps :)
> You can always call PSS and get a free incident opened and ask the same
> question...just give them the KB article number when you call,
> --
> Kevin Hill
> 3NF Consultinghttp://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:http://kevin3nf.blogspot.com
>
> > The KB Article mentions. BUG #: 483 (SQL Hotfix). What makes you say
> > this is not a SQL hotfix?
> > Terry- Hide quoted text -
> - Show quoted text -
Thank you Kevin. Your efforts and responses are greatly appreciated.
Terry
Subscribe to:
Posts (Atom)