Monday, February 27, 2012
Hot-Swappable dimensions
model we have several hot-swappable (sub)dimensions which is linked to
a large dimension table. All dimensions are type 2. I don't think that
this is correct because when the data in the sub-dimension is changing
we need a new record in the large dimension too, otherwise you lose
the history of the record.
Instead I would like to create one FK in the Fact table which is
linked to all sub-dimensions. Because this key needs to be unique over
all sub-dimensions I am thinking about using a uniqueidentifier (16
byte GUID) field.
Is this the correct approach?
At a later stage at least 4 new hot-swappable dimensions will be
introduced.On May 2, 11:35 am, LuCarD <j...@.lucard.nl> wrote:
> We are in the middle of creating a dataware house. In the current
> model we have several hot-swappable (sub)dimensions which is linked to
> a large dimension table. All dimensions are type 2. I don't think that
> this is correct because when the data in the sub-dimension is changing
> we need a new record in the large dimension too, otherwise you lose
> the history of the record.
> Instead I would like to create one FK in the Fact table which is
> linked to all sub-dimensions. Because this key needs to be unique over
> all sub-dimensions I am thinking about using a uniqueidentifier (16
> byte GUID) field.
> Is this the correct approach?
> At a later stage at least 4 new hot-swappable dimensions will be
> introduced.
If you are going to create more than 2^31 record in the sub-dimension
table, probably you have to split that in several dimensions with a
reduced number of different values. Denormalizing the sub-dimension
into a "regular" dimension could be a good idea (it depends on many
other factors) but in this case there is no reason to continue using
surrogate keys with a tiny size (int or even smallint if you can).
When you have this data on the fact table, actually you preserved
history and you don't need to use SCD type 2 for these dimensions.
If you want to do more complex analysis, like "give me the sales of
this months projected on the organizational structure we had one year
ago", then you need to design a more complex model that will be much
difficult (and slow) to query, unless you use a particular OLAP model
like some of those described in the many-to-many paper you can find
here: http://www.sqlbi.eu/manytomany.aspx
Marco Russo
http://www.sqlbi.eu
http://sqlblog.com/blogs/marco_russo
Hot-Swappable dimensions
model we have several hot-swappable (sub)dimensions which is linked to
a large dimension table. All dimensions are type 2. I don't think that
this is correct because when the data in the sub-dimension is changing
we need a new record in the large dimension too, otherwise you lose
the history of the record.
Instead I would like to create one FK in the Fact table which is
linked to all sub-dimensions. Because this key needs to be unique over
all sub-dimensions I am thinking about using a uniqueidentifier (16
byte GUID) field.
Is this the correct approach?
At a later stage at least 4 new hot-swappable dimensions will be
introduced.
On May 2, 11:35 am, LuCarD <j...@.lucard.nl> wrote:
> We are in the middle of creating a dataware house. In the current
> model we have several hot-swappable (sub)dimensions which is linked to
> a large dimension table. All dimensions are type 2. I don't think that
> this is correct because when the data in the sub-dimension is changing
> we need a new record in the large dimension too, otherwise you lose
> the history of the record.
> Instead I would like to create one FK in the Fact table which is
> linked to all sub-dimensions. Because this key needs to be unique over
> all sub-dimensions I am thinking about using a uniqueidentifier (16
> byte GUID) field.
> Is this the correct approach?
> At a later stage at least 4 new hot-swappable dimensions will be
> introduced.
If you are going to create more than 2^31 record in the sub-dimension
table, probably you have to split that in several dimensions with a
reduced number of different values. Denormalizing the sub-dimension
into a "regular" dimension could be a good idea (it depends on many
other factors) but in this case there is no reason to continue using
surrogate keys with a tiny size (int or even smallint if you can).
When you have this data on the fact table, actually you preserved
history and you don't need to use SCD type 2 for these dimensions.
If you want to do more complex analysis, like "give me the sales of
this months projected on the organizational structure we had one year
ago", then you need to design a more complex model that will be much
difficult (and slow) to query, unless you use a particular OLAP model
like some of those described in the many-to-many paper you can find
here: http://www.sqlbi.eu/manytomany.aspx
Marco Russo
http://www.sqlbi.eu
http://sqlblog.com/blogs/marco_russo
Hot-standby SQL Server Using Alias Name?
SQL on two separate machines, SRVA and SRVB, and configure continuous merge
replication between them. Client machines would connect to an alias name,
SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon failure, DNS
would be changed to point to SRVB. Could something like this work? If so, how
would one start to implement it?
Maybe a shorther question would be, is it possible for clients to connect to a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric RobinsonThis is a multi-part message in MIME format.
--=_NextPart_000_0370_01C3A9EA.14018070
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
Consider using a clustered installation of SQL Server. It has automatic
failover and requires no human intervention.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Eric Robinson" <eric@._nospam_nvipa.com> wrote in message
news:CFN379384331352315@.news.microsoft.com...
I want to have a hot standby SQL server for my clients. My idea is to
install
SQL on two separate machines, SRVA and SRVB, and configure continuous merge
replication between them. Client machines would connect to an alias name,
SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon failure,
DNS
would be changed to point to SRVB. Could something like this work? If so,
how
would one start to implement it?
Maybe a shorther question would be, is it possible for clients to connect to
a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric Robinson
--=_NextPart_000_0370_01C3A9EA.14018070
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Consider using a clustered =installation of SQL Server. It has automatic failover and requires no human intervention.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Eric Robinson"
--=_NextPart_000_0370_01C3A9EA.14018070--
hotkey to uncomment
I searched online help and googled and for the life of me cant remember
Hi g
If you are talking about the SQL 2000 Query Analyzer, you can go to the Edit
Menu, and choose Advanced (at the bottom). The Advanced Options include both
Comment and Remove Comments, and they will show you what the hot keys are.
Remove Comments (Uncomment) is CTRL-SHIFT-R
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"g" <gregoranton_nospamplease_@.hotmail.com> wrote in message
news:prJIf.1960$n67.838@.edtnps89...
> CTRL-SHIFT-C comments code, what do you use to uncomment?
> I searched online help and googled and for the life of me cant remember
>
hotfixes, mssqlsystemresource.ldf
have moved the 'mssqlsystemresource.ldf' logfile to a different
subirectory from the MDF.
It is well documented that the mssqlsystemresource.mdf must be in the
same location as master.mdf, but I haven't seen anything about keeping
the ldf with the mdf (our practice is to run with LDF files on a
different set of spindles from the MDF files).
If you have this setup and haven't done a service pack, you can readily
fix it by moving the LDF from the MDF folder and putting it where it
'belongs' according to the master catalog.
However, you're better off leaving both the LDF and MDF together with
master.mdf.> However, you're better off leaving both the LDF and MDF together with
> master.mdf.
Yes, this is the Best Practice. Unfortunately, it's easy to forget about
those mssqlsystemresource files.
Hope this helps.
Dan Guzman
SQL Server MVP
"horseradish" <millardjk@.gmail.com> wrote in message
news:OWUWEgDuHHA.4412@.TK2MSFTNGP02.phx.gbl...
> I've just discovered that applying a hotfix to SQL2005 can fail if you
> have moved the 'mssqlsystemresource.ldf' logfile to a different
> subirectory from the MDF.
> It is well documented that the mssqlsystemresource.mdf must be in the same
> location as master.mdf, but I haven't seen anything about keeping the ldf
> with the mdf (our practice is to run with LDF files on a different set of
> spindles from the MDF files).
> If you have this setup and haven't done a service pack, you can readily
> fix it by moving the LDF from the MDF folder and putting it where it
> 'belongs' according to the master catalog.
> However, you're better off leaving both the LDF and MDF together with
> master.mdf.
hotfixes, mssqlsystemresource.ldf
have moved the 'mssqlsystemresource.ldf' logfile to a different
subirectory from the MDF.
It is well documented that the mssqlsystemresource.mdf must be in the
same location as master.mdf, but I haven't seen anything about keeping
the ldf with the mdf (our practice is to run with LDF files on a
different set of spindles from the MDF files).
If you have this setup and haven't done a service pack, you can readily
fix it by moving the LDF from the MDF folder and putting it where it
'belongs' according to the master catalog.
However, you're better off leaving both the LDF and MDF together with
master.mdf.
> However, you're better off leaving both the LDF and MDF together with
> master.mdf.
Yes, this is the Best Practice. Unfortunately, it's easy to forget about
those mssqlsystemresource files.
Hope this helps.
Dan Guzman
SQL Server MVP
"horseradish" <millardjk@.gmail.com> wrote in message
news:OWUWEgDuHHA.4412@.TK2MSFTNGP02.phx.gbl...
> I've just discovered that applying a hotfix to SQL2005 can fail if you
> have moved the 'mssqlsystemresource.ldf' logfile to a different
> subirectory from the MDF.
> It is well documented that the mssqlsystemresource.mdf must be in the same
> location as master.mdf, but I haven't seen anything about keeping the ldf
> with the mdf (our practice is to run with LDF files on a different set of
> spindles from the MDF files).
> If you have this setup and haven't done a service pack, you can readily
> fix it by moving the LDF from the MDF folder and putting it where it
> 'belongs' according to the master catalog.
> However, you're better off leaving both the LDF and MDF together with
> master.mdf.
hotfixes, mssqlsystemresource.ldf
have moved the 'mssqlsystemresource.ldf' logfile to a different
subirectory from the MDF.
It is well documented that the mssqlsystemresource.mdf must be in the
same location as master.mdf, but I haven't seen anything about keeping
the ldf with the mdf (our practice is to run with LDF files on a
different set of spindles from the MDF files).
If you have this setup and haven't done a service pack, you can readily
fix it by moving the LDF from the MDF folder and putting it where it
'belongs' according to the master catalog.
However, you're better off leaving both the LDF and MDF together with
master.mdf.> However, you're better off leaving both the LDF and MDF together with
> master.mdf.
Yes, this is the Best Practice. Unfortunately, it's easy to forget about
those mssqlsystemresource files.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"horseradish" <millardjk@.gmail.com> wrote in message
news:OWUWEgDuHHA.4412@.TK2MSFTNGP02.phx.gbl...
> I've just discovered that applying a hotfix to SQL2005 can fail if you
> have moved the 'mssqlsystemresource.ldf' logfile to a different
> subirectory from the MDF.
> It is well documented that the mssqlsystemresource.mdf must be in the same
> location as master.mdf, but I haven't seen anything about keeping the ldf
> with the mdf (our practice is to run with LDF files on a different set of
> spindles from the MDF files).
> If you have this setup and haven't done a service pack, you can readily
> fix it by moving the LDF from the MDF folder and putting it where it
> 'belongs' according to the master catalog.
> However, you're better off leaving both the LDF and MDF together with
> master.mdf.
Hotfixes available SQL Server
Is there a MS service available or a MS site that lists all (not just secuirty related) generally available hotfixes for SQL Server?
I am aware of the security notification. And also the information available here.
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
Just wondering if I can be alerted when all new hotfixes are available.
TIA
take a look at http://support.microsoft.com/default.aspx?kbid=290211 a link
seems to list all the fixes.
Tim S
"Joe" <anonymous@.discussions.microsoft.com> wrote in message
news:6549916A-680D-4F9F-A848-A4FA25F01CF1@.microsoft.com...
> Hello,
> Is there a MS service available or a MS site that lists all (not just
secuirty related) generally available hotfixes for SQL Server?
> I am aware of the security notification. And also the information
available here.
> http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
> Just wondering if I can be alerted when all new hotfixes are available.
> TIA
>
Hotfixes available SQL Server
Is there a MS service available or a MS site that lists all (not just secuir
ty related) generally available hotfixes for SQL Server?
I am aware of the security notification. And also the information available
here.
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
Just wondering if I can be alerted when all new hotfixes are available.
TIAtake a look at http://support.microsoft.com/default.aspx?kbid=290211 a link
seems to list all the fixes.
Tim S
"Joe" <anonymous@.discussions.microsoft.com> wrote in message
news:6549916A-680D-4F9F-A848-A4FA25F01CF1@.microsoft.com...
> Hello,
> Is there a MS service available or a MS site that lists all (not just
secuirty related) generally available hotfixes for SQL Server?
> I am aware of the security notification. And also the information
available here.
> http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
> Just wondering if I can be alerted when all new hotfixes are available.
> TIA
>
hotfixes - general question
post sp3(a).
TIA,
JBHave a look at :
http://support.microsoft.com/common...=&maxresults=20
Rgds,
Paul Ibison (SQL Server MVP)|||Personally, I like the guys at the SQL Security website.
Try this:
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
Sincerely,
Anthony Thomas
--
"JB" <anonymous@.discussions.microsoft.com> wrote in message news:95c501c4d
489$1b02c170$a401280a@.phx.gbl...
Whaer can I get a list of the hotfixes/interim builds etc
post sp3(a).
TIA,
JB
hotfixes - general question
post sp3(a).
TIA,
JB
Have a look at :
http://support.microsoft.com/common/...&maxresults=20
Rgds,
Paul Ibison (SQL Server MVP)
|||Personally, I like the guys at the SQL Security website.
Try this:
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
Sincerely,
Anthony Thomas
"JB" <anonymous@.discussions.microsoft.com> wrote in message news:95c501c4d489$1b02c170$a401280a@.phx.gbl...
Whaer can I get a list of the hotfixes/interim builds etc
post sp3(a).
TIA,
JB
hotfixes - general question
post sp3(a).
TIA,
JBHave a look at :
http://support.microsoft.com/common/canned.aspx?r=d&h=microsoft%20sql%20server%202000%20post-sp3%20hotfixes&ll=&sz=kbsqlserv2000presp4fix&fr=&du=&sd=gn&ln=en-us&cnd=1&vr=&cat=&vrl=&sg=&maxresults=20
Rgds,
Paul Ibison (SQL Server MVP)
hotfix/service pack directory
(fairly) comprehensive list of hotfixes, service packs and cumulative
update packs for SQL Server.
Anyone care to re-post?
Maybe Aaron Bertrand's blog?
http://sqlblog.com/blogs/aaron_bertrand/default.aspx
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"horseradish" wrote:
> I remember seeing a post in this newsgroup for a website maintaining a
> (fairly) comprehensive list of hotfixes, service packs and cumulative
> update packs for SQL Server.
> Anyone care to re-post?
>
|||take a look here
http://www.aspfaq.com/sql2005/show.asp?id=20
and here
http://www.aspfaq.com/sql2000Builds.asp
Denis The SQL Menace
http://sqlservercode.blogspot.com
http://sqlblog.com/blogs/denis_gobo/default.aspx
On Nov 27, 4:34 pm, horseradish <dontcal...@.illcallu.net> wrote:
> I remember seeing a post in this newsgroup for a website maintaining a
> (fairly) comprehensive list of hotfixes, service packs and cumulative
> update packs for SQL Server.
> Anyone care to re-post?
|||Check this one
http://sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx
Manu
"horseradish" wrote:
> I remember seeing a post in this newsgroup for a website maintaining a
> (fairly) comprehensive list of hotfixes, service packs and cumulative
> update packs for SQL Server.
> Anyone care to re-post?
>
hotfix/service pack directory
(fairly) comprehensive list of hotfixes, service packs and cumulative
update packs for SQL Server.
Anyone care to re-post?Maybe Aaron Bertrand's blog?
http://sqlblog.com/blogs/aaron_bertrand/default.aspx
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"horseradish" wrote:
> I remember seeing a post in this newsgroup for a website maintaining a
> (fairly) comprehensive list of hotfixes, service packs and cumulative
> update packs for SQL Server.
> Anyone care to re-post?
>|||take a look here
http://www.aspfaq.com/sql2005/show.asp?id=20
and here
http://www.aspfaq.com/sql2000Builds.asp
Denis The SQL Menace
http://sqlservercode.blogspot.com
http://sqlblog.com/blogs/denis_gobo/default.aspx
On Nov 27, 4:34 pm, horseradish <dontcal...@.illcallu.net> wrote:
> I remember seeing a post in this newsgroup for a website maintaining a
> (fairly) comprehensive list of hotfixes, service packs and cumulative
> update packs for SQL Server.
> Anyone care to re-post?|||Check this one
http://sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx
Manu
"horseradish" wrote:
> I remember seeing a post in this newsgroup for a website maintaining a
> (fairly) comprehensive list of hotfixes, service packs and cumulative
> update packs for SQL Server.
> Anyone care to re-post?
>|||It must be this one =)
http://sqlserverbuilds.blogspot.com/
--
Ekrem Önsoy
"horseradish" <dontcallme@.illcallu.net> wrote in message
news:Ot30H1TMIHA.6060@.TK2MSFTNGP05.phx.gbl...
>I remember seeing a post in this newsgroup for a website maintaining a
>(fairly) comprehensive list of hotfixes, service packs and cumulative
>update packs for SQL Server.
> Anyone care to re-post?
hotfix/service pack directory
(fairly) comprehensive list of hotfixes, service packs and cumulative
update packs for SQL Server.
Anyone care to re-post?Maybe Aaron Bertrand's blog?
http://sqlblog.com/blogs/aaron_bertrand/default.aspx
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"horseradish" wrote:
> I remember seeing a post in this newsgroup for a website maintaining a
> (fairly) comprehensive list of hotfixes, service packs and cumulative
> update packs for SQL Server.
> Anyone care to re-post?
>|||take a look here
http://www.aspfaq.com/sql2005/show.asp?id=20
and here
http://www.aspfaq.com/sql2000Builds.asp
Denis The SQL Menace
http://sqlservercode.blogspot.com
http://sqlblog.com/blogs/denis_gobo/default.aspx
On Nov 27, 4:34 pm, horseradish <dontcal...@.illcallu.net> wrote:
> I remember seeing a post in this newsgroup for a website maintaining a
> (fairly) comprehensive list of hotfixes, service packs and cumulative
> update packs for SQL Server.
> Anyone care to re-post?|||Check this one
http://sqlsecurity.com/FAQs/SQLServ...63/Default.aspx
Manu
"horseradish" wrote:
> I remember seeing a post in this newsgroup for a website maintaining a
> (fairly) comprehensive list of hotfixes, service packs and cumulative
> update packs for SQL Server.
> Anyone care to re-post?
>|||It must be this one =)
http://sqlserverbuilds.blogspot.com/
Ekrem nsoy
"horseradish" <dontcallme@.illcallu.net> wrote in message
news:Ot30H1TMIHA.6060@.TK2MSFTNGP05.phx.gbl...
>I remember seeing a post in this newsgroup for a website maintaining a
>(fairly) comprehensive list of hotfixes, service packs and cumulative
>update packs for SQL Server.
> Anyone care to re-post?
Hotfix Versions
Is there someplace where I can find a definitve reference as to which
hotfix has been installed and relate that to the version shown by
'SELECT @.@.VERSION' post SQL Server 2000 SP3?
Most references I have found stop at SP3.
Many thanks
Simonhttp://www.aspfaq.com/show.asp?id=2160
Jacco Schalkwijk
SQL Server MVP
"Simon Adams" <warmtea@.hotmail.com> wrote in message
news:c34aa6c2.0502160534.4f3e04f6@.posting.google.com...
> Hi,
> Is there someplace where I can find a definitve reference as to which
> hotfix has been installed and relate that to the version shown by
> 'SELECT @.@.VERSION' post SQL Server 2000 SP3?
> Most references I have found stop at SP3.
> Many thanks
> Simon
Hotfix Versions
Is there someplace where I can find a definitve reference as to which
hotfix has been installed and relate that to the version shown by
'SELECT @.@.VERSION' post SQL Server 2000 SP3?
Most references I have found stop at SP3.
Many thanks
Simon
http://www.aspfaq.com/show.asp?id=2160
Jacco Schalkwijk
SQL Server MVP
"Simon Adams" <warmtea@.hotmail.com> wrote in message
news:c34aa6c2.0502160534.4f3e04f6@.posting.google.c om...
> Hi,
> Is there someplace where I can find a definitve reference as to which
> hotfix has been installed and relate that to the version shown by
> 'SELECT @.@.VERSION' post SQL Server 2000 SP3?
> Most references I have found stop at SP3.
> Many thanks
> Simon
Hotfix Versions
Is there someplace where I can find a definitve reference as to which
hotfix has been installed and relate that to the version shown by
'SELECT @.@.VERSION' post SQL Server 2000 SP3?
Most references I have found stop at SP3.
Many thanks
Simonhttp://www.aspfaq.com/show.asp?id=2160
--
Jacco Schalkwijk
SQL Server MVP
"Simon Adams" <warmtea@.hotmail.com> wrote in message
news:c34aa6c2.0502160534.4f3e04f6@.posting.google.com...
> Hi,
> Is there someplace where I can find a definitve reference as to which
> hotfix has been installed and relate that to the version shown by
> 'SELECT @.@.VERSION' post SQL Server 2000 SP3?
> Most references I have found stop at SP3.
> Many thanks
> Simon
hotfix verfication....
SP4 hotfix is this? Thanks.Rob,
This is the one.
INF: SQL Server 7.0 Security Update for Service Pack 4
http://support.microsoft.com/default.aspx?scid=kb;en-us;327068
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Rob" <rhchin@.hotmail.com> wrote in message
news:0e8101c360e0$3b1fb3a0$a601280a@.phx.gbl...
> My SQL Server 7.0 version returns - 7.00.1077. What post
> SP4 hotfix is this? Thanks.|||http://www.aspfaq.com/2160
"Rob" <rhchin@.hotmail.com> wrote in message
news:0e8101c360e0$3b1fb3a0$a601280a@.phx.gbl...
> My SQL Server 7.0 version returns - 7.00.1077. What post
> SP4 hotfix is this? Thanks.
Hotfix Question
all necessary hotfixes since SP3a individually.
Thanks for your help
Oscar
Hi
Yes they are, unless the readme documentation indicates it.
0952 includes 0818, 0878 etc.
Regards
Mike
"Oscar" wrote:
> Can anyone tell me if SQL server hotfixes are cumulative? Right now we apply
> all necessary hotfixes since SP3a individually.
> Thanks for your help
> Oscar
>
Hotfix Question
all necessary hotfixes since SP3a individually.
Thanks for your help
OscarHi
Yes they are, unless the readme documentation indicates it.
0952 includes 0818, 0878 etc.
Regards
Mike
"Oscar" wrote:
> Can anyone tell me if SQL server hotfixes are cumulative? Right now we apply
> all necessary hotfixes since SP3a individually.
> Thanks for your help
> Oscar
>
Hotfix Question
y
all necessary hotfixes since SP3a individually.
Thanks for your help
OscarHi
Yes they are, unless the readme documentation indicates it.
0952 includes 0818, 0878 etc.
Regards
Mike
"Oscar" wrote:
> Can anyone tell me if SQL server hotfixes are cumulative? Right now we ap
ply
> all necessary hotfixes since SP3a individually.
> Thanks for your help
> Oscar
>
Hotfix Post SP4
I am searching for a list of published hotfix posted after SQL Server SP4.
Is there such a link or URL, on the Microsoft site?
Thank you for your time.
Franco
Nope. You kind of have to poke around. There are 3 post-SP4 hotfixes that
I am aware of:
Build 2040, to fix the AWE memory issue.
Build 2148, to fix the SQLDiag issue, but also fixes another 10 or so.
Build 2151, to fix the Query Analyzer DTC issue.
This site can be helpful though.
SQL Server Version Database
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
Otherwise, you are stuck searching through the Microsoft Support site.
Build 2040:
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
http://support.microsoft.com/default...b;en-us;899761
Build 2148:
FIX: An access violation may occur when a deadlock graph is written to the
error log in SQL Server 2000
http://support.microsoft.com/default...b;en-us;898626
FIX: An access violation may occur when you run a SELECT query and the
NO_BROWSETABLE option is set to ON in Microsoft SQL Server 2000
http://support.microsoft.com/default...b;en-us;899430
FIX: An access violation occurs in the Mssdi98.dll file, and SQL Server
crashes when you use SQL Query Analyzer to debug a stored procedure in SQL
Server 2000 Service Pack 4
http://support.microsoft.com/default...b;en-us;899431
FIX: The Mssdmn.exe process may use lots of CPU capacity when you perform a
SQL Server 2000 full text search of Office Word documents
http://support.microsoft.com/default...b;en-us;900390
FIX: The results of the query may be returned much slower than you expect
when you run a query that includes a GROUP BY statement in SQL Server 2000
http://support.microsoft.com/default...b;en-us;900404
FIX: You receive a "Failed to open a table" error message when you try to
open a trace table by using SQL Profiler after you upgrade to SQL Server
2000 Service Pack 4
http://support.microsoft.com/default...b;en-us;900629
FIX: You may receive a "Server: Msg 7358, Level 16, State 1, Line 1" error
message after you run a linked server query in SQL Server 2000 Service Pack
4
http://support.microsoft.com/default...b;en-us;901200
FIX: You receive an error message if you use the sp_addalias or sp_dropalias
procedures when the IMPLICIT_TRANSACTIONS option is set to ON in SQL Server
2000 SP4
http://support.microsoft.com/default...b;en-us;901212
FIX: Some 32-bit applications that use SQL-DMO and SQL-VDI APIs may stop
working after you install SQL Server 2000 Service Pack 4 on an Itanium-based
computer
http://support.microsoft.com/default...b;en-us;902150
FIX: You receive a "Getting registry information" message when you run the
Sqldiag.exe utility after you install SQL Server 2000 SP4
http://support.microsoft.com/default...b;en-us;902955
FIX: The batch job stops running, and job output is truncated when you run a
Transact-SQL script as a SQL Server Agent job in SQL Server 2000
http://support.microsoft.com/default...b;en-us;903086
Build 2151:
FIX: You receive an "Error: 8526, Severity: 16, State: 2" error message in
SQL Profiler when you use SQL Query Analyzer to start or to enlist into a
distributed transaction after you have installed SQL Server 2000 SP4
http://support.microsoft.com/default...b;en-us;903742
Sincerely,
Anthony Thomas
"Franco" <Franco@.discussions.microsoft.com> wrote in message
news:6C7551B7-1250-4504-B844-D81BCCDEF252@.microsoft.com...
> Hi all,
> I am searching for a list of published hotfix posted after SQL Server SP4.
> Is there such a link or URL, on the Microsoft site?
> Thank you for your time.
> --
> Franco
|||Thank you very much.
I really appreciate your answer.
Kind regards.
Franco
"Anthony Thomas" wrote:
> Nope. You kind of have to poke around. There are 3 post-SP4 hotfixes that
> I am aware of:
> Build 2040, to fix the AWE memory issue.
> Build 2148, to fix the SQLDiag issue, but also fixes another 10 or so.
> Build 2151, to fix the Query Analyzer DTC issue.
> This site can be helpful though.
>
> SQL Server Version Database
> http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
>
> Otherwise, you are stuck searching through the Microsoft Support site.
>
> Build 2040:
> 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
> http://support.microsoft.com/default...b;en-us;899761
>
> Build 2148:
> FIX: An access violation may occur when a deadlock graph is written to the
> error log in SQL Server 2000
> http://support.microsoft.com/default...b;en-us;898626
> FIX: An access violation may occur when you run a SELECT query and the
> NO_BROWSETABLE option is set to ON in Microsoft SQL Server 2000
> http://support.microsoft.com/default...b;en-us;899430
> FIX: An access violation occurs in the Mssdi98.dll file, and SQL Server
> crashes when you use SQL Query Analyzer to debug a stored procedure in SQL
> Server 2000 Service Pack 4
> http://support.microsoft.com/default...b;en-us;899431
> FIX: The Mssdmn.exe process may use lots of CPU capacity when you perform a
> SQL Server 2000 full text search of Office Word documents
> http://support.microsoft.com/default...b;en-us;900390
> FIX: The results of the query may be returned much slower than you expect
> when you run a query that includes a GROUP BY statement in SQL Server 2000
> http://support.microsoft.com/default...b;en-us;900404
> FIX: You receive a "Failed to open a table" error message when you try to
> open a trace table by using SQL Profiler after you upgrade to SQL Server
> 2000 Service Pack 4
> http://support.microsoft.com/default...b;en-us;900629
> FIX: You may receive a "Server: Msg 7358, Level 16, State 1, Line 1" error
> message after you run a linked server query in SQL Server 2000 Service Pack
> 4
> http://support.microsoft.com/default...b;en-us;901200
> FIX: You receive an error message if you use the sp_addalias or sp_dropalias
> procedures when the IMPLICIT_TRANSACTIONS option is set to ON in SQL Server
> 2000 SP4
> http://support.microsoft.com/default...b;en-us;901212
> FIX: Some 32-bit applications that use SQL-DMO and SQL-VDI APIs may stop
> working after you install SQL Server 2000 Service Pack 4 on an Itanium-based
> computer
> http://support.microsoft.com/default...b;en-us;902150
> FIX: You receive a "Getting registry information" message when you run the
> Sqldiag.exe utility after you install SQL Server 2000 SP4
> http://support.microsoft.com/default...b;en-us;902955
> FIX: The batch job stops running, and job output is truncated when you run a
> Transact-SQL script as a SQL Server Agent job in SQL Server 2000
> http://support.microsoft.com/default...b;en-us;903086
>
> Build 2151:
> FIX: You receive an "Error: 8526, Severity: 16, State: 2" error message in
> SQL Profiler when you use SQL Query Analyzer to start or to enlist into a
> distributed transaction after you have installed SQL Server 2000 SP4
> http://support.microsoft.com/default...b;en-us;903742
>
> Sincerely,
>
> Anthony Thomas
>
> --
> "Franco" <Franco@.discussions.microsoft.com> wrote in message
> news:6C7551B7-1250-4504-B844-D81BCCDEF252@.microsoft.com...
>
>
Hotfix on sp2
Hello,
Just want to know if anybody else has problems with the hotfix ?
I have a sqlserver 2005 on my desktop.
I installed the sp2 before 5th march.
Recently Microsoft changed the sp2 and released a hotfix for sp2 installed(downloaded) before 5th march.
I installed the hotfix but it failed to update the sqlserver engine.
Very weird.
I uninstalled sqlserver 2005, applied the new sp2 (which was smaller compared with previous one)
Today i still received a critical update in windows update.
I installed it, but i still don't trust these updates.
How can i investigate all went well ?
Go to Add/Remove Programs, click on the SQL 2005 entry, click Remove, and then Change. This will show a nice report at the component level and include the versions for each. If they are all at 3152, then your machine is up to date with the cumulative hotfix. If not, go grab it here:
http://support.microsoft.com/kb/933097
Thanks,
Sam Lester (MSFT)
Hotfix on sp2
Hello,
Just want to know if anybody else has problems with the hotfix ?
I have a sqlserver 2005 on my desktop.
I installed the sp2 before 5th march.
Recently Microsoft changed the sp2 and released a hotfix for sp2 installed(downloaded) before 5th march.
I installed the hotfix but it failed to update the sqlserver engine.
Very weird.
I uninstalled sqlserver 2005, applied the new sp2 (which was smaller compared with previous one)
Today i still received a critical update in windows update.
I installed it, but i still don't trust these updates.
How can i investigate all went well ?
Go to Add/Remove Programs, click on the SQL 2005 entry, click Remove, and then Change. This will show a nice report at the component level and include the versions for each. If they are all at 3152, then your machine is up to date with the cumulative hotfix. If not, go grab it here:
http://support.microsoft.com/kb/933097
Thanks,
Sam Lester (MSFT)
Hotfix needed
The kb article (http://support.microsoft.com/?kbid=830466)
says to contact microsoft customer service. When I ask for
free online support it asks for the product id. When I try
to check where the pid is, it's not listed. Our licenseing
folks have no idea what our pid is for sql server.
You can find the product ID in the registry key
HKLM\Software\Microsoft\Microsoft SQL Server\80\Registration\ProductID
Jacco Schalkwijk
SQL Server MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
|||You can get a newer fix (878), which includes the fixes for 852, here:
http://support.microsoft.com/?kbid=838166
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
Hotfix needed
The kb article (http://support.microsoft.com/?kbid=830466)
says to contact microsoft customer service. When I ask for
free online support it asks for the product id. When I try
to check where the pid is, it's not listed. Our licenseing
folks have no idea what our pid is for sql server.You can find the product ID in the registry key
HKLM\Software\Microsoft\Microsoft SQL Server\80\Registration\ProductID
--
Jacco Schalkwijk
SQL Server MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.|||You can get a newer fix (878), which includes the fixes for 852, here:
http://support.microsoft.com/?kbid=838166
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
Hotfix needed
The kb article (http://support.microsoft.com/?kbid=830466)
says to contact microsoft customer service. When I ask for
free online support it asks for the product id. When I try
to check where the pid is, it's not listed. Our licenseing
folks have no idea what our pid is for sql server.You can find the product ID in the registry key
HKLM\Software\Microsoft\Microsoft SQL Server\80\Registration\ProductID
Jacco Schalkwijk
SQL Server MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.|||You can get a newer fix (878), which includes the fixes for 852, here:
http://support.microsoft.com/?kbid=838166
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
Hotfix Installation failed on named Instance on a SQL-Server-2000 Cluster
I have a windows 2003 cluster
with sql-server 2000 sp3
and a named instance.
I wanted to installation the hotfix ..859, but the installation failed
and I got the error:
"The logged on account does not have administrator privileges on all
possible owner nodes of the selected SQL Server configuration.
Please log on using an account that has administrator privileges on all
possible owner nodes and then run Hotfix Installer again."
I've checked different things.
My account has the correct rights, the RPC service is running, DNS
works fine ...
I have no idea what to do!
Can someone help?
Greetings
Susn
Are you running the hotfix from the controlling node? Also, you may have to
reboot each node, before the hotfix will install.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
<liebesusn@.web.de> wrote in message
news:1106919750.693602.235970@.f14g2000cwb.googlegr oups.com...
> Hi all,
> I have a windows 2003 cluster
> with sql-server 2000 sp3
> and a named instance.
> I wanted to installation the hotfix ..859, but the installation failed
> and I got the error:
> "The logged on account does not have administrator privileges on all
> possible owner nodes of the selected SQL Server configuration.
> Please log on using an account that has administrator privileges on all
> possible owner nodes and then run Hotfix Installer again."
> I've checked different things.
> My account has the correct rights, the RPC service is running, DNS
> works fine ...
> I have no idea what to do!
> Can someone help?
> Greetings
> Susn
>
|||Hi Rod,
yes, the hotfix was running from the controlling node and both nodes
was rebooted.
Any other idea?
Greetings Susn
|||No, that about does it for me, sorry!
Rod
"Susn" <liebesusn@.web.de> wrote in message
news:1107160932.634056.6880@.c13g2000cwb.googlegrou ps.com...
> Hi Rod,
> yes, the hotfix was running from the controlling node and both nodes
> was rebooted.
> Any other idea?
> Greetings Susn
>
|||Hi Susn,
Just wondering if you were able to install the hotfix. I would recommend you to log into both the nodes of the cluster with the startup account of the clustered SQL Server service (this account is a doman account and
should have all the required rights). Then start the hotfix installation on the node where SQL Server instance is currently running.
Keep up updated. If it fails, then please post the log for the hotfix failure.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
Hotfix from KB821334
2000 SP3a? It looks like you have to contact PSS to get any hotfixes
anymore. Does that mean anyone new to Reporting Services has to contact PSS
just to be able to install Reporting Services?Well, that's what we had to do.
--
Adrian M.
MCP
"Tim Paulsen" <Tim Paulsen@.discussions.microsoft.com> wrote in message
news:4B6D804D-435C-4810-A200-913E5A744322@.microsoft.com...
> What happened to the hotfix required by Reporting Services for SQL Server
> 2000 SP3a? It looks like you have to contact PSS to get any hotfixes
> anymore. Does that mean anyone new to Reporting Services has to contact
> PSS
> just to be able to install Reporting Services?|||Good question. Hotfix 859 is required if installing on Windows 2003 Server
(which means almost everybody needs it). I'll ask this in the SQL Server MVP
forum and see what is up and provide the answer on this thread.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Tim Paulsen" <Tim Paulsen@.discussions.microsoft.com> wrote in message
news:4B6D804D-435C-4810-A200-913E5A744322@.microsoft.com...
> What happened to the hotfix required by Reporting Services for SQL Server
> 2000 SP3a? It looks like you have to contact PSS to get any hotfixes
> anymore. Does that mean anyone new to Reporting Services has to contact
PSS
> just to be able to install Reporting Services?|||My investigation (not official from MS) shows that most documentation has
been updated to refer to SP4 (which would have this hotfix rolled up in it).
So could be that SP4 will be soon and that would be what people would apply
instead of the hotfix. For now, contacting PSS seems to be the only route to
take.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Tim Paulsen" <Tim Paulsen@.discussions.microsoft.com> wrote in message
news:4B6D804D-435C-4810-A200-913E5A744322@.microsoft.com...
> What happened to the hotfix required by Reporting Services for SQL Server
> 2000 SP3a? It looks like you have to contact PSS to get any hotfixes
> anymore. Does that mean anyone new to Reporting Services has to contact
> PSS
> just to be able to install Reporting Services?
hotfix for: KB816939 (PRB: File Growth Value for TempDB is Not Per
Changed From Fixed Increments to Percentage):
Does anyone know if microsoft has included a fix for this in sp4, or has a
hotfix for this bug?
We tried the workaround listed in the KB, but it did not work...
Link:
http://support.microsoft.com/defaul...n-us;816939#kb4Can you give more info regarding how the work around did not work?
As far as I know the fix did not make it into SP4...
It is fixed in SQL 2005 though.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:FF219273-52D1-42C0-8CE5-35CDF27E01BD@.microsoft.com...
> Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent
When
> Changed From Fixed Increments to Percentage):
> Does anyone know if microsoft has included a fix for this in sp4, or has a
> hotfix for this bug?
> We tried the workaround listed in the KB, but it did not work...
> Link:
> http://support.microsoft.com/defaul...n-us;816939#kb4
hotfix for: KB816939 (PRB: File Growth Value for TempDB is Not Per
Changed From Fixed Increments to Percentage):
Does anyone know if microsoft has included a fix for this in sp4, or has a
hotfix for this bug?
We tried the workaround listed in the KB, but it did not work...
Link:
http://support.microsoft.com/default...-us;816939#kb4
Can you give more info regarding how the work around did not work?
As far as I know the fix did not make it into SP4...
It is fixed in SQL 2005 though.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:FF219273-52D1-42C0-8CE5-35CDF27E01BD@.microsoft.com...
> Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent
When
> Changed From Fixed Increments to Percentage):
> Does anyone know if microsoft has included a fix for this in sp4, or has a
> hotfix for this bug?
> We tried the workaround listed in the KB, but it did not work...
> Link:
> http://support.microsoft.com/default...-us;816939#kb4
hotfix for: KB816939 (PRB: File Growth Value for TempDB is Not Per
Changed From Fixed Increments to Percentage):
Does anyone know if microsoft has included a fix for this in sp4, or has a
hotfix for this bug?
We tried the workaround listed in the KB, but it did not work...
Link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816939#kb4Can you give more info regarding how the work around did not work?
As far as I know the fix did not make it into SP4...
It is fixed in SQL 2005 though.
--
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:FF219273-52D1-42C0-8CE5-35CDF27E01BD@.microsoft.com...
> Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent
When
> Changed From Fixed Increments to Percentage):
> Does anyone know if microsoft has included a fix for this in sp4, or has a
> hotfix for this bug?
> We tried the workaround listed in the KB, but it did not work...
> Link:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;816939#kb4
Hotfix for SP1 didn't work. There is still no Select All option.
I installed SP1 on a box running SQL Server 2005. I was puzzled as to why the Select All option had disappeared on my multi-value parameters. I found out on on this message board that the SP1 install removed this option. I contacted Microsoft yesterday and after being on hold for over 75 minutes, I was asble to speak with someone who sent me an email containing a link to the hotfix download. I installed the hotfix, rebooted the server, and my reports still do not have the Select All option. Has anyone else had this problem? I sent an email to the support rep I was in contact with at Microsoft but I was hoping that someone here might have some suggestions while I wait to here from Microsoft.
Any thoughts would be greatly appreciated. Thanks!
Amedeo
The removal of Select All is by design, so I would recommend just using the work around rather than trying the hotfix. I modified all my reports after SP1, and it isn't a big deal to implement. Here's a starting point.
http://msdn2.microsoft.com/en-US/library/aa337234.aspx
|||If I understand your suggestion correctly, you are stating I should try the "ALL" parameter in place of the (Select All) option once provided by SSRS. I followed the article listed below and it worked great. Although it is a really good workaround, the reason I want the (Select All) that originally came with SSRS is because when you choose or unchoose (Select All) it checks or unchecks all of the boxes for the other parameter choices.
http://blogs.msdn.com/chrishays/archive/2006/04/18/AllParameterValueRedux.aspx
I'm working with an engineer from Microsoft right now as to why the hotfix didn't work. I'll be sure to post the solution assuming there is one.
|||I don't know how difficult it would be, but maybe you could write some custom code that would select all your multi-select options. Good luck on finding the answer.|||I worked with several different people at Microsoft regarding this issue and I wanted to share the solution. Just to clarify my initial post, there were several patches I had to run in order to install the hotfix. One of the patches would not successfully install. The problem was that IIS still thought it had a SSL certificate when it really didn't.
Clean up the certificate by going to IIS Manager and removing the certificate from IIS. When you rerun setup, it should succeed. This link was very helpful.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=90906&SiteID=1
|||Where can I get the patches?|||If you would like to get a patch before SP2 is released, you have tocontact Support Services and ask for Knowledge Base Article #919478
Hotfix for SP1 didn't work. There is still no Select All option.
I installed SP1 on a box running SQL Server 2005. I was puzzled as to why the Select All option had disappeared on my multi-value parameters. I found out on on this message board that the SP1 install removed this option. I contacted Microsoft yesterday and after being on hold for over 75 minutes, I was asble to speak with someone who sent me an email containing a link to the hotfix download. I installed the hotfix, rebooted the server, and my reports still do not have the Select All option. Has anyone else had this problem? I sent an email to the support rep I was in contact with at Microsoft but I was hoping that someone here might have some suggestions while I wait to here from Microsoft.
Any thoughts would be greatly appreciated. Thanks!
Amedeo
The removal of Select All is by design, so I would recommend just using the work around rather than trying the hotfix. I modified all my reports after SP1, and it isn't a big deal to implement. Here's a starting point.
http://msdn2.microsoft.com/en-US/library/aa337234.aspx
|||If I understand your suggestion correctly, you are stating I should try the "ALL" parameter in place of the (Select All) option once provided by SSRS. I followed the article listed below and it worked great. Although it is a really good workaround, the reason I want the (Select All) that originally came with SSRS is because when you choose or unchoose (Select All) it checks or unchecks all of the boxes for the other parameter choices.
http://blogs.msdn.com/chrishays/archive/2006/04/18/AllParameterValueRedux.aspx
I'm working with an engineer from Microsoft right now as to why the hotfix didn't work. I'll be sure to post the solution assuming there is one.
|||I don't know how difficult it would be, but maybe you could write some custom code that would select all your multi-select options. Good luck on finding the answer.|||I worked with several different people at Microsoft regarding this issue and I wanted to share the solution. Just to clarify my initial post, there were several patches I had to run in order to install the hotfix. One of the patches would not successfully install. The problem was that IIS still thought it had a SSL certificate when it really didn't.
Clean up the certificate by going to IIS Manager and removing the certificate from IIS. When you rerun setup, it should succeed. This link was very helpful.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=90906&SiteID=1
|||Where can I get the patches?|||If you would like to get a patch before SP2 is released, you have tocontact Support Services and ask for Knowledge Base Article #919478
Hotfix for SP1 didn't work. There is still no Select All option.
I installed SP1 on a box running SQL Server 2005. I was puzzled as to why the Select All option had disappeared on my multi-value parameters. I found out on on this message board that the SP1 install removed this option. I contacted Microsoft yesterday and after being on hold for over 75 minutes, I was asble to speak with someone who sent me an email containing a link to the hotfix download. I installed the hotfix, rebooted the server, and my reports still do not have the Select All option. Has anyone else had this problem? I sent an email to the support rep I was in contact with at Microsoft but I was hoping that someone here might have some suggestions while I wait to here from Microsoft.
Any thoughts would be greatly appreciated. Thanks!
Amedeo
The removal of Select All is by design, so I would recommend just using the work around rather than trying the hotfix. I modified all my reports after SP1, and it isn't a big deal to implement. Here's a starting point.
http://msdn2.microsoft.com/en-US/library/aa337234.aspx
|||If I understand your suggestion correctly, you are stating I should try the "ALL" parameter in place of the (Select All) option once provided by SSRS. I followed the article listed below and it worked great. Although it is a really good workaround, the reason I want the (Select All) that originally came with SSRS is because when you choose or unchoose (Select All) it checks or unchecks all of the boxes for the other parameter choices.
http://blogs.msdn.com/chrishays/archive/2006/04/18/AllParameterValueRedux.aspx
I'm working with an engineer from Microsoft right now as to why the hotfix didn't work. I'll be sure to post the solution assuming there is one.
|||I don't know how difficult it would be, but maybe you could write some custom code that would select all your multi-select options. Good luck on finding the answer.|||I worked with several different people at Microsoft regarding this issue and I wanted to share the solution. Just to clarify my initial post, there were several patches I had to run in order to install the hotfix. One of the patches would not successfully install. The problem was that IIS still thought it had a SSL certificate when it really didn't.
Clean up the certificate by going to IIS Manager and removing the certificate from IIS. When you rerun setup, it should succeed. This link was very helpful.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=90906&SiteID=1
|||Where can I get the patches?|||If you would like to get a patch before SP2 is released, you have tocontact Support Services and ask for Knowledge Base Article #919478
hotfix for KB884554
ThanksYou would need to contact MS support
http://support.microsoft.com/defaul...Bln%5D;cntactms
If you show that you have the problem it should be free.
Chris Wood
"Igor" <Igor@.discussions.microsoft.com> wrote in message
news:AE51DA1E-2C47-43CB-9857-E4D59611E2E5@.microsoft.com...
> How or where can I obtain hotfix for article KB884554?
> Thanks|||I forgot. Its also part of SP4 beta and SP4 RTM coming soon.
Chris
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23OgoanTFFHA.2156@.TK2MSFTNGP10.phx.gbl...
> You would need to contact MS support
> http://support.microsoft.com/defaul...Bln%5D;cntactms
> If you show that you have the problem it should be free.
> Chris Wood
> "Igor" <Igor@.discussions.microsoft.com> wrote in message
> news:AE51DA1E-2C47-43CB-9857-E4D59611E2E5@.microsoft.com...
>
hotfix for KB884554
Thanks
You would need to contact MS support
http://support.microsoft.com/default...ln%5D;cntactms
If you show that you have the problem it should be free.
Chris Wood
"Igor" <Igor@.discussions.microsoft.com> wrote in message
news:AE51DA1E-2C47-43CB-9857-E4D59611E2E5@.microsoft.com...
> How or where can I obtain hotfix for article KB884554?
> Thanks
|||I forgot. Its also part of SP4 beta and SP4 RTM coming soon.
Chris
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23OgoanTFFHA.2156@.TK2MSFTNGP10.phx.gbl...
> You would need to contact MS support
> http://support.microsoft.com/default...ln%5D;cntactms
> If you show that you have the problem it should be free.
> Chris Wood
> "Igor" <Igor@.discussions.microsoft.com> wrote in message
> news:AE51DA1E-2C47-43CB-9857-E4D59611E2E5@.microsoft.com...
>
hotfix for KB884554
ThanksYou would need to contact MS support
http://support.microsoft.com/default.aspx?scid=fh;%5Bln%5D;cntactms
If you show that you have the problem it should be free.
Chris Wood
"Igor" <Igor@.discussions.microsoft.com> wrote in message
news:AE51DA1E-2C47-43CB-9857-E4D59611E2E5@.microsoft.com...
> How or where can I obtain hotfix for article KB884554?
> Thanks|||I forgot. Its also part of SP4 beta and SP4 RTM coming soon.
Chris
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23OgoanTFFHA.2156@.TK2MSFTNGP10.phx.gbl...
> You would need to contact MS support
> http://support.microsoft.com/default.aspx?scid=fh;%5Bln%5D;cntactms
> If you show that you have the problem it should be free.
> Chris Wood
> "Igor" <Igor@.discussions.microsoft.com> wrote in message
> news:AE51DA1E-2C47-43CB-9857-E4D59611E2E5@.microsoft.com...
>> How or where can I obtain hotfix for article KB884554?
>> Thanks
>
Hotfix for Bug # 473675 (SQL Server could not spawn process_loginread thread)
Hi,
I get "SQL Server could not spawn process_loginread thread." errors. This is related to a bug in SQL 2000 and there is a hotfix for SP3a.
I am running SQL2000 with SP4. I checked the fix list of SP4 & this bug is not fixed in this SP4.
Can I apply the hotfix to resolve this problem on my server?
tia.
Hi,
SP4 is a superset of SP3,SP2,SP1
So this hotfix must be included in SP4.
You can't easily relate error messages and hotfixes, it could be another reason you are getting this message. Read carefully what the hotfix fixes, relate it to the situation you are dealing with and judge if the hotfix is relevant enough to your problem, so as to risk applying it.
Some more info (complete error message, hotfix info, when and where you get the error message) would help
|||I am also facing the same problem..though we are using SP3.
Will upgrading to SP4 help?
Do we need to do something else to get rid of the problem?
|||The most common cause of this message is a lack of free virtual address space. The most common cause of virtual address starvation on SQL 2000 are misbehaving com components from the use of sp_oacreate, misbehaving extended stored procedures, or poorly written OLEDB providers that are loaded by the use of linked servers.
Start by reviewing your use of these items and remove them from the system as possible.
|||
Jerome,
This is an event that happens on our production server about once a week. It only lasts for 2-5 minutes. We are running SQL 2000 SP4. Is there any way to adjust the memory allocation?
Thanks in advance.
Ron
Hotfix for Bug # 473675 (SQL Server could not spawn process_loginread thread)
Hi,
I get "SQL Server could not spawn process_loginread thread." errors. This is related to a bug in SQL 2000 and there is a hotfix for SP3a.
I am running SQL2000 with SP4. I checked the fix list of SP4 & this bug is not fixed in this SP4.
Can I apply the hotfix to resolve this problem on my server?
tia.
Hi,
SP4 is a superset of SP3,SP2,SP1
So this hotfix must be included in SP4.
You can't easily relate error messages and hotfixes, it could be another reason you are getting this message. Read carefully what the hotfix fixes, relate it to the situation you are dealing with and judge if the hotfix is relevant enough to your problem, so as to risk applying it.
Some more info (complete error message, hotfix info, when and where you get the error message) would help
|||I am also facing the same problem..though we are using SP3.
Will upgrading to SP4 help?
Do we need to do something else to get rid of the problem?
|||The most common cause of this message is a lack of free virtual address space. The most common cause of virtual address starvation on SQL 2000 are misbehaving com components from the use of sp_oacreate, misbehaving extended stored procedures, or poorly written OLEDB providers that are loaded by the use of linked servers.
Start by reviewing your use of these items and remove them from the system as possible.
|||
Jerome,
This is an event that happens on our production server about once a week. It only lasts for 2-5 minutes. We are running SQL 2000 SP4. Is there any way to adjust the memory allocation?
Thanks in advance.
Ron
Hotfix for Bug # 473675 (SQL Server could not spawn process_loginread thread)
Hi,
I get "SQL Server could not spawn process_loginread thread." errors. This is related to a bug in SQL 2000 and there is a hotfix for SP3a.
I am running SQL2000 with SP4. I checked the fix list of SP4 & this bug is not fixed in this SP4.
Can I apply the hotfix to resolve this problem on my server?
tia.
Hi,
SP4 is a superset of SP3,SP2,SP1
So this hotfix must be included in SP4.
You can't easily relate error messages and hotfixes, it could be another reason you are getting this message. Read carefully what the hotfix fixes, relate it to the situation you are dealing with and judge if the hotfix is relevant enough to your problem, so as to risk applying it.
Some more info (complete error message, hotfix info, when and where you get the error message) would help
|||I am also facing the same problem..though we are using SP3.
Will upgrading to SP4 help?
Do we need to do something else to get rid of the problem?
|||The most common cause of this message is a lack of free virtual address space. The most common cause of virtual address starvation on SQL 2000 are misbehaving com components from the use of sp_oacreate, misbehaving extended stored procedures, or poorly written OLEDB providers that are loaded by the use of linked servers.
Start by reviewing your use of these items and remove them from the system as possible.
|||
Jerome,
This is an event that happens on our production server about once a week. It only lasts for 2-5 minutes. We are running SQL 2000 SP4. Is there any way to adjust the memory allocation?
Thanks in advance.
Ron
Hotfix for article 831997
After I applied 8.00.0859, I am now getting the
error "Invalid Cursor State" when in design mode of the
Enterprise Manager.
Thanks!
Did you actually need to apply 8.00.859? I've found that in most cases
people applied this hotfix merely because it was available to the general
public. The reason hotfixes aren't announced and made more readily
accessible is because they aren't fully regression tested, and aren't immune
to issues like this one.
In any case, you can get 878 from http://support.microsoft.com/?kbid=838166
...
Also, see http://www.aspfaq.com/2515 ... if you stop using Enterprise
Manager for data/schema manipulation, amazingly, the invalid cursor state
error goes away.
http://www.aspfaq.com/
(Reverse address to reply.)
"Troy Anderson" <tanderso@.sonoma-county.org> wrote in message
news:2817301c46384$d0604720$a301280a@.phx.gbl...
> How can I obtain the Hotfix noted in Article 831997.
> After I applied 8.00.0859, I am now getting the
> error "Invalid Cursor State" when in design mode of the
> Enterprise Manager.
> Thanks!
|||If you are needing a hotfix, you'd best contact Microsoft PSS Support and
ask for the hotfix. Hotfixes are grace (free) cases.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Hotfix for article 831997
After I applied 8.00.0859, I am now getting the
error "Invalid Cursor State" when in design mode of the
Enterprise Manager.
Thanks!Did you actually need to apply 8.00.859? I've found that in most cases
people applied this hotfix merely because it was available to the general
public. The reason hotfixes aren't announced and made more readily
accessible is because they aren't fully regression tested, and aren't immune
to issues like this one.
In any case, you can get 878 from http://support.microsoft.com/?kbid=838166
...
Also, see http://www.aspfaq.com/2515 ... if you stop using Enterprise
Manager for data/schema manipulation, amazingly, the invalid cursor state
error goes away.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Troy Anderson" <tanderso@.sonoma-county.org> wrote in message
news:2817301c46384$d0604720$a301280a@.phx.gbl...
> How can I obtain the Hotfix noted in Article 831997.
> After I applied 8.00.0859, I am now getting the
> error "Invalid Cursor State" when in design mode of the
> Enterprise Manager.
> Thanks!|||If you are needing a hotfix, you'd best contact Microsoft PSS Support and
ask for the hotfix. Hotfixes are grace (free) cases.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Hotfix for article 831997
After I applied 8.00.0859, I am now getting the
error "Invalid Cursor State" when in design mode of the
Enterprise Manager.
Thanks!Did you actually need to apply 8.00.859? I've found that in most cases
people applied this hotfix merely because it was available to the general
public. The reason hotfixes aren't announced and made more readily
accessible is because they aren't fully regression tested, and aren't immune
to issues like this one.
In any case, you can get 878 from http://support.microsoft.com/?kbid=838166
...
Also, see http://www.aspfaq.com/2515 ... if you stop using Enterprise
Manager for data/schema manipulation, amazingly, the invalid cursor state
error goes away.
http://www.aspfaq.com/
(Reverse address to reply.)
"Troy Anderson" <tanderso@.sonoma-county.org> wrote in message
news:2817301c46384$d0604720$a301280a@.phx
.gbl...
> How can I obtain the Hotfix noted in Article 831997.
> After I applied 8.00.0859, I am now getting the
> error "Invalid Cursor State" when in design mode of the
> Enterprise Manager.
> Thanks!|||If you are needing a hotfix, you'd best contact Microsoft PSS Support and
ask for the hotfix. Hotfixes are grace (free) cases.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Friday, February 24, 2012
Hotfix for 826906 in SP4?
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.
Hotfix fixed my SQL Server
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...[vbcol=seagreen]
> I have the same problem. Did you get a fix?
> Thanks!
> ~ Troy
>
> the Microsoft site,
> here
> the previous hotfix
> Support Services" to
> you can pay to
> a link to it
> why this one is so
Hotfix fixed my SQL Server
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
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
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...[vbcol=seagreen]
> I have the same problem. Did you get a fix?
> Thanks!
> ~ Troy
> the Microsoft site,
> here
> the previous hotfix
> Support Services" to
> you can pay to
> a link to it
> why this one is so
Hotfix fixed my SQL Server
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.
> >
> >
> >.
> >