Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Date Calculation Spin Error/Warning Messages Expand / Collapse
Author
Message
Posted Friday, September 26, 2008 9:54 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, February 28, 2014 8:49 AM
Points: 211, Visits: 125
Has anyone see messages similar to the following on their SQL 2005 box?

[191] Warning [1]: Possible date calculation spin for Schedule 64
[192] Date calculation spin detected for Schedule 64

It's the first time I saw them on my SQL 2005 box. I found the following reference: FIX: SQLAgent Job with Recurring Schedule is Disabled Upon Completion of the Schedule for the Day (KB295378), which is for SQL 2000. But didn't find information related to SQL 2005. Checked and none of my SQL agent jobs were disabled.

Appreciate any insight you may have regarding the issue.
Post #576979
Posted Friday, September 26, 2008 11:37 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 15,444, Visits: 9,596
I haven't run into that, but my best guess it that I would check which jobs were on schedule 64 and see if there's any issue with any of them. Might need to build a parallel schedule and use that instead, if something is corrupted in the main schedule.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #577052
Posted Friday, September 26, 2008 11:48 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, February 28, 2014 8:49 AM
Points: 211, Visits: 125
Thanks for your reply. I did check all my jobs and job histories to make sure they are working correctly.

What puzzles me is that, as indicated in the KB article, this is a problem for SQL 2000 and 7.0, and was corrected by sp1 for SQL 2000 and sp4 for SQL 7.0. So I assume it's not an issue for SQL 2005 anymore and wonder why I got it.
Post #577058
Posted Friday, September 26, 2008 2:29 PM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 15,444, Visits: 9,596
No clue why you got it. Maybe a job ported over from SQL 2000 and with something messed up by that?

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #577162
Posted Friday, July 30, 2010 3:57 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Friday, August 1, 2014 6:18 AM
Points: 1,618, Visits: 20,980
Can you please try changing the start date of the job to today, for the ones which have very old start date?

Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
Post #961216
Posted Thursday, September 9, 2010 8:15 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, September 10, 2010 12:34 PM
Points: 30, Visits: 49
I'm getting this error on a 08 Enterprise Server sp2, running SQL 08. This is a brand new install that hosts Sharepoint 07.
I've got standard backup jobs a moss delete expired session job and the syspolicy_purge job.
Nothing out of the ordinary and nothing different than 6 other db servers that I'm running with the same config.
Everything I've read is old and related to 00, or 05 instances. any ideas?


[191] Warning [4]: Possible date calculation spin for Schedule 12
Post #983113
Posted Wednesday, September 26, 2012 8:27 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, October 21, 2013 7:49 AM
Points: 15, Visits: 270
It can occur because of SNAPSHOT_ISOLATION_LEVEL on your db.
Need drop\create the table with error
Post #1364734
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse