BUG: 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.aspx?scid=kb;en-us;899761

This seems to be a pretty significant issue missed by the "more rigorous
regression testing" for Service Pack releases.  I would have expected
something like this for a QFE or hotfix, but for a Service Pack!

Is Microsoft considering an SP4a substitution or just another QFE and/or
hotfix?  This is a major blunder that makes us all look bad!

Good luck getting approvals from our managers to update our production
systems in the future.  Luckily, we had only started our QA/QC deployments.

Frustrated,

Anthony Thomas

I thought the Beta was suppose to be locked down.  At least that what was
told us at the pre-SP4 webcast.

SP4 Beta, build 8.00.2026, SP4 public release, build 8.00.2039.  That's 13
fixes between beta and final release.

What good is a Beta program if last minute changes can be introduced like
this?

We DEMAND answers!


Anthony Thomas


BUG: 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.aspx?scid=kb;en-us;899761

This seems to be a pretty significant issue missed by the "more rigorous
regression testing" for Service Pack releases.  I would have expected
something like this for a QFE or hotfix, but for a Service Pack!

Is Microsoft considering an SP4a substitution or just another QFE and/or
hotfix?  This is a major blunder that makes us all look bad!

Good luck getting approvals from our managers to update our production
systems in the future.  Luckily, we had only started our QA/QC deployments.

Frustrated,

Anthony Thomas

Anthony Thomas wrote:
Show quoteHide quoteI spoke with MS today regarding this issue and another in SP4. The
HotFix for the AWE issue is complete and being tested. I would expect to
see it available in a week or two at the outside. The HotFix will be
available for download from the MS web site.

Anyone expereincing the problem with Profiler SP4 that is preventing
them from opening a trace table in Profiler will have a fix in about 3
weeks (refer to the not-yet-posted KB article #: 900629). PSS will have
to be contacted for the HotFix (no charge for the call).

Good to hear that they are "on it;" however, that does little for the
stability, or the cofidence, in the platform.  That was a pretty big bug to
have missed for an SP release.

I realize how we go through these types of issues, but the cofidence level
of our organization, and, particularly, our group's credibility will not be
an easy thing to overcome.

Thanks for the response.

Sincerely,


Anthony Thomas


Anthony Thomas wrote:
Show quoteHide quoteI spoke with MS today regarding this issue and another in SP4. The
HotFix for the AWE issue is complete and being tested. I would expect to
see it available in a week or two at the outside. The HotFix will be
available for download from the MS web site.

Anyone expereincing the problem with Profiler SP4 that is preventing
them from opening a trace table in Profiler will have a fix in about 3
weeks (refer to the not-yet-posted KB article #: 900629). PSS will have
to be contacted for the HotFix (no charge for the call).

David,

Did you hear anything about a hotfix that would restore the fix for 826906
("A query that uses a view that contains a correlated subquery and an
aggregate runs slowly") into SP4?  Will that be part of the AWE hotfix?  Or
in a separate hotfix?

Regards,

Jonathan

Jonathan Levine wrote:
Show quoteHide quoteI have no information on that particular hotfix. What I can tell you is
that there will be additional fixes included in the AWE hotfix. All
hotfixes are normally cumulative. I'm guessing that the 826906 hotfix
was released at a point after the branch for SP4 was made. I wouldn't be
surprised if that fix makes it in.

Additionally, PSS just handles support calls you wish to call MS with a
problem... They are not responsible to fix bugs in the software, that would
be the dev team... So, in this case, PSS is innocent.

Show quoteHide quote

You are absolutely correct; however, PSS, unfortunate as it is, is the
public "interface": you can not contact the "dev" team directly—high-level
contacts aside.

What really astounds me is the lack of conversation regarding this.  This
particular bug is drastic; unfortunately, it only affects the larger
installations, which is NOT the primary usage for SQL Server.  However, it
is the bigger installations that are the most important, and, more
unfortunately, happens to be several of mine.

I'm sure it is gettting through, but I am highly shocked that not only did
this happen but also with the way it is being handled...discretely, like
every other issue.  This was a screw up and MS should come clean and do
something to restore confidence.  Keeping silent is NOT working.

Anthony Thomas


Additionally, PSS just handles support calls you wish to call MS with a
problem... They are not responsible to fix bugs in the software, that would
be the dev team... So, in this case, PSS is innocent.

Show quoteHide quote

Basic question.... on Index....
Problem with osql.exe -L
Simple Question: What's the best way to duplicate a DB under another name?
full drives full trans log version 7
alter table drop column and dbcc cleantable
SQL7 2 DB files down to one???
Server: Msg 7391, Level 16, State 1, Procedure <OBJECT>, Line
varchar vs nvarchar
stored procedure with different criteria
Autonumber