BUG: Daily Tasks May Be Disabled If Activestartdate = 0

 Last reviewed: May 28, 1997
Article ID: Q169164
The information in this article applies to:
  • Microsoft SQL Server, version 6.0 and 6.5
BUG #: 16930 (NT: 6.5)

SYMPTOMS

If you use sp_addtask to create a Transact-SQL daily task with activestartdate = 0, and the task is run successfully at least once, the task will be disabled upon SQL Executive startup if SQL Executive is stopped and not restarted for a sufficient amount of time. The time period varies from 1-5 days, depending on the frequency of the task. This behavior only occurs with Transact-SQL daily tasks, but will occur whether the daily frequency is once, every x minutes, or every x hours.

WORKAROUND

To work around this problem, create the task through the SQL Enterprise Manager.

Insert a valid non-zero value for activestartdate if you are using sp_addtask. The current date in the format YYYYMMDD is best.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The sp_addtask SQL Executive Stored Procedure section of the SQL Server Books Online states: 

   activestartdate
   Specifies the date when this task will first be scheduled. Formatted as
   YYYYMMDD. The default is 0.
However, when you create a task through SQL Enterprise Manager, the current date is inserted for activestartdate. Therefore, this problem only occurs if you use the sp_addtask stored procedure to create the task.

Keywords : kbbug6.00 kbbug6.50 kbusage SSrvTran_SQL
Version : 6.0 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbworkaround

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: May 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.