FIX: Some Task Management St. Procs. Accept Some Invalid Dates

Last reviewed: December 31, 1998
Article ID: Q192958

The information in this article applies to:
  • Microsoft SQL Server version 6.5
BUG #: 18180, 18170 (SQLBUG_65)

SYMPTOMS

The following stored procedures

sp_addtask(@activestartdate,@activeenddate,@nextrundate) sp_purgehistory(@startdate,@enddate) sp_updatealert(@count_reset_date,@last_occurrence_date,@last_response_date)

Accept the following as incoming date parameters: 

   2/29/1999
   1/0/2000
   2/30/2000
   2/31/2000
   2/29/2001
These dates do not exist, and should not be available.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in the latest U.S. Service Pack for SQL Server version 6.5. For more information, contact your primary support provider.

Additional query words: prodsqlYear2000 y2k year2k 2000 st proc SP SPs sp5
Keywords : kbbug6.50 SSrvStProc kbfix6.50.sp5
Version : WINNT:6.5
Platform : winnt
Issue type : kbbug

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 31, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.