Re: float point error

From: Anthony Thomas (ALThomas_at_kc.rr.com)
Date: 01/24/05 

Date: Sun, 23 Jan 2005 19:46:05 -0600

Yes, I found this out with .0859. The biggest reason I jumped on .0878, it
seemed more stable.

I also noticed the large build increase on deploying the SP4 Beta (2026?)
However, from the fix list off of the beta description, it only includes
fixes through .0972 and I've seen KB listing all the way up to .1000 +. So,
I'm not sure how a Build including only fixes to the 972 level could be
labeled 2026. That's got me stumped. Not to mention that it bombs the
replication if you've already applied 878. I've got that thread running in
the Beta newsgroup.

Now, I wouldn't want to slam PSS, because they've been very helpful,
especially in crash circumstances; however, they have been known to push hot
fixes a little too eagerly as well. I figure once it has gone public, at
least, it has somewhat stabilized. But yes, I realize, that even SP level
code bases can introduce new bugs.

As always, thanks for your insight.

Sincerely,

Anthony Thomas 

-- 
"Aaron [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:%23zfCiKbAFHA.3940@TK2MSFTNGP09.phx.gbl...
> As you know, SQL Server QFEs are cumulative.
That is true until .977.  For example, to install .993 on .760, you first
need to get to the .977 hotfix installer -- .993 won't install on < .977 (it
will complain about missing prerequisites).
> The fix described in this
> article is Build 2000.00.0807.  The latest publicly available hot fix is
> Build .0878, which would include a fix for this error.
However, it is not always the best to just install the latest.  He may
prefer to go through PSS, demonstrate that .807 is his issue, and fix that.
.878 might bring about other problems that he doesn't have time to fully
test.  Sure, it might be more convenient to get a patch that is publicly
available, but I don't jump to the conclusion that it is absolutely the best
answer.
> Also know that SP4 is currently in Beta testing and will include builds up
> to .0972.
And then the numbering scheme jumps significantly (SP4 beta is .2026, yet
there are several .973+ hotfixes already available).
I'm still curious why they chose to break at .977 to use the new hotfix
installer, breaking the chain of cumulative hotfixes.  It would have been a
much more logical break, IMHO, to wait for SP4 -- introduce the new hotfix
installer at a stable, fully tested service pack... <shrug>
A

Relevant Pages

  • FreeBSD 5.3-BETA6 available
    ... help find and/or fix bugs. ... The 5.3 release cycle will continue with ... weekly BETA builds while bugs are being fixed and features finalized. ... Fixes and Enhancements made since BETA5: ...
    (freebsd-current)
  • Re: USB - wince5.0
    ... I also refer WINCE 6.0 Beta and try to fix this issue. ... void BulUsbDevice::PowerDown ... Does SetDevicePowerState will effect suspend/resume? ...
    (microsoft.public.windowsce.platbuilder)
  • 5.3-BETA5 Available
    ... help find and/or fix bugs. ... The 5.3 release cycle will continue with ... weekly BETA builds while bugs are being fixed and features finalized. ... Fixes and Enhancements made since BETA4: ...
    (freebsd-current)
  • Re: WSS v3 Beta Event 6398 and what worked for me
    ... and all newsgroup links are back to the regular public ... lots of other problems could not figure out how to fix. ... Please post all SharePoint Beta posts to the Public Community specifically ...
    (microsoft.public.sharepoint.portalserver)
  • Re: float point error
    ... they have to cut the beta release off at some point. ... asked about the build number with no response though. ... > I also noticed the large build increase on deploying the SP4 Beta > However, from the fix list off of the beta description, it only includes ... clearly we can't be testing everything right up to the point of release, and we're already using a build that's behind on at least 6 unique hotfixes so far. ...
    (microsoft.public.sqlserver.server)