|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 2:24 AM
Points: 1,871,
Visits: 2,692
|
|
Comments posted to this topic are about the item SQL 6.5 and Y2K
---------------------------------------------- Msg 8134, Level 16, State 1, Line 1 Divide by zero error encountered.
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 4:00 PM
Points: 5,102,
Visits: 20,205
|
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Today @ 12:39 AM
Points: 1,846,
Visits: 976
|
|
I did not any thing about SQL 6.5 ,7.0.Also i did little work on SQL server 2000.Worked mostly on 2005 and 2008.This question is almost ten years old.
Malleswarareddy I.T.Analyst MCITP(70-451)
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Monday, April 22, 2013 11:48 PM
Points: 160,
Visits: 63
|
|
| that one should have been filed under 'pointless', anyone still concerned with the Y2K compliance of version 6.5 has bigger issues
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Friday, November 30, 2012 1:52 AM
Points: 1,116,
Visits: 602
|
|
I did the right guess! :)
10 Years ago I wasn't SQL Server aware, since then I upgraded myself a few times to what I am now...
Ronald Hensbergen
Help us, help yourself... Post data so we can read and use it: http://www.sqlservercentral.com/articles/Best+Practices/61537/ ------------------------------------------------------------------------- 2+2=5 for significant large values of 2
|
|
|
|
|
SSCoach
         
Group: General Forum Members
Last Login: 2 days ago @ 1:07 PM
Points: 18,733,
Visits: 12,332
|
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 1:41 AM
Points: 3,190,
Visits: 4,147
|
|
The question forces to make an archaeological excavation
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 2:24 AM
Points: 1,871,
Visits: 2,692
|
|
Jason, I'm actually aware of a few places who are forced by legacy apps to run 6.5....and by the looks of this:
Correct answers: 38% (54) Incorrect answers: 62% (89) Total attempts: 143
not too many people were/are aware of the y2k issue on 6.5.
---------------------------------------------- Msg 8134, Level 16, State 1, Line 1 Divide by zero error encountered.
|
|
|
|
|
UDP Broadcaster
      
Group: General Forum Members
Last Login: Friday, May 10, 2013 3:15 AM
Points: 1,476,
Visits: 1,943
|
|
Henrico Bekker (8/13/2010) Jason, I'm actually aware of a few places who are forced by legacy apps to run 6.5....and by the looks of this:
Correct answers: 38% (54) Incorrect answers: 62% (89) Total attempts: 143
not too many people were/are aware of the y2k issue on 6.5.
Which really doesnt matter. Because if your where to get any problems because of this you would already have gotten them.
And no i dont know if there where some patches needed for Windows 95/98 to make them Y2K compatible as well either.
Do i care... no. Is it important... no. Is it fun... no. Is it relevant... no. Did i learn something... no. Valuable leason... no. Waste of time... yes. Is writing this replay pointless... yes. Is it Friday... YES
And by that note ur forgiven 
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Thursday, January 24, 2013 9:59 PM
Points: 1,354,
Visits: 1,299
|
|
Although I did get the answer right, I had to pick the closest response to the correct answer.
Technically, it was version 6.50.339 that fixed the Y2K issue. Then, Service Pack 5 came out (version 6.50.415) which was defective and you shouldn't have used it. Then, Service Pack 5a (version 6.50.416) released.
So, you could have fixed the Y2K problem before the release of SP5a if you installed the "Y2K" hot fix to the 6.50.281 (SP4) or 6.50.297 versions.
|
|
|
|