In SQL Server 2000, is possible for a Job Schedule to become Corrupt? and if so, how does that happen? The observed behavior, was an error being thrown that the number 75 was not a proper MIN or MAX and the schedule would not open for editing. (The job has been running on this schedule has been running for 3 weeks) I removed the the schedule and created a new one successfully. I also did integrity checks on MSDB, MASTER, and the user databases and no errors were reported. This question is more for satisfying my curiosity than anything else. I have been doing DBA work for 12+ years and I can honestly say, I have never seen this before. Very much appreciate any input on the topic To all the Veterans out there 'Thank You" and Happy Veterans Day!, Happy Remembrance Day!