Microsoft battles Y2K compliance

Microsoft battles Y2K compliance

Microsoft later this quarter will fix a year 2000 problem related to the scheduling engine in the SQL Server 6.5 database.

A scheduling engine used to fire off batch processes requires repair to ensure that it recognises the year 2000 as a leap year, said Doug Leland, Microsoft's lead product manager for SQL Server.

The issue focuses on setting the expiration date for batch processes and the capability to overwrite it with a certain date.

A fix will be in the release of SQL Server, Service Pack 5.0, which is due this quarter. Microsoft officials would not detail what other features will be in Service Pack 5.0, but did note that SQL Server 6.5 would be cleansed of any remaining year-2000 issues.

Microsoft's service packs feature incremental improvements and bug fixes that would otherwise have to wait until a new release of the database.

Service Pack 4.0, released June 30, didn't address the leap-year issue, a Microsoft representative said.

Microsoft's technique for the storage of data formats has been in compliance with the year 2000, but there remain issues to be dealt with in peripheral areas.

Resolving those remaining issues in SQL Server 6.5 means that users will not have to upgrade to SQL Server 7.0 in order to achieve full year-2000 compliance on Microsoft's database platform.

SQL Server, Version 7.0, is due to be released by the end of this year.

Although Microsoft officially has said its Office applications are now year-2000 compliant, there have been nuances in how products interpret the year 2000 in different versions of the Office package.

Follow Us

Join the newsletter!


Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.


Show Comments