| Author |
Topic |
|
kdog
Starting Member
14 Posts |
 Posted - 2006-01-10 : 14:48:12
|
| Hi all, I have a dts package that is scheduled to run every 5 minutes, Monday - Saturday from 9AM to 9PM. But every morning when I check the job it isn't running. The actual job itself is enabled, but when I look at the details of the job i.e "schedules" tab it shows the schedule disabled. I have to enable the schedule everyday - a super pain in #%#%. Anyone have any idea what could be causing this too happen?btw - I'm using SQL 2000 Standard |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-01-10 : 16:30:06
|
| If it is set to run a single time then the schedule is disabled and you need to re-enable it when you change it to recurring - maybe someone is doing that.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-01-10 : 16:38:43
|
| It must be a recurring schedule in order for it to work as desired. What are you selecting when you add the schedule back in?Tara Kizeraka tduggan |
|
|
|
kdog
Starting Member
14 Posts |
Posted - 2006-01-10 : 17:05:25
|
| NR - The schedule is set to reoccuring weekly for Monday, Tuesday, Thursday, Friday and Saturday - there is no end date. I am the only person with rights to log into this database.tkizer - To re-enable I:1. I double-click the job. 2. Then click on the "Schedules" tab.3. Highlight my schedule in the list.4. click the "edit" button at the bottom.5. A new dialog appears. I 'click on' the enable option at the top of this dialog.6. Apply changes.After that the package will continue to run correctly for the rest of the day. The next day the schedule disables itself...kdog |
|
|
|
kdog
Starting Member
14 Posts |
Posted - 2006-01-10 : 17:07:42
|
| correction to last post:I should have said the package runs Monday, Tuesday, Wednesday, Thursday, Friday and Saturday (I left out Wednesday on last post). Not that this little detail is going to matter... |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-01-10 : 17:07:57
|
| Perhaps you've encountered a bug. What does SELECT @@VERSION show? Are you able to create similar jobs without problems? Could you create a dummy job with the same schedule to see if it gets disabled?I'd suggest running SQL Profiler during the time that the schedule gets disabled to see what is doing it.Tara Kizeraka tduggan |
|
|
|
kdog
Starting Member
14 Posts |
Posted - 2006-01-10 : 17:23:06
|
| tkizer, I get for version:"Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)"I have another package scheduled to run every 5 minutes and is weekly for multiple days and it has the same bug. Also, I have a few other packages that are set weekly for multiple days but NOT set to run every 5 minutes - these schedules work fine and don't need to be re-enabled everyday.I'll try profiler, although I have little experience using it and I'm not sure what I would be looking for...I'm assuming that the schedule disables after 9PM. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-01-10 : 17:26:02
|
| 8.00.194 - you are many versions behind. You should either install service pack 4 OR service pack 3a plus security patch 818.Tara Kizeraka tduggan |
|
|
|
kdog
Starting Member
14 Posts |
Posted - 2006-01-10 : 18:59:33
|
| doh &%#%I just installed service pack 4...see what happens tomorrow ;) |
|
|
|
kdog
Starting Member
14 Posts |
Posted - 2006-01-11 : 09:17:12
|
| Thanks tkizer. The jobs are running as scheduled today - it looks like SP4 did the trick.Thanks Again! |
|
|
|
|
SQL Schedules have minds of their own?