dts scheduler doesn't remember my settings 1

[NuJoizey]

I got my package all set up the way I want it, so now I want to schedule it, so I right click my package and choose 'schedule' - but it doesn't want to let me schedule the package!

I go into the scheduling wizard and set it up for say, once a week every Monday, but then if I right click and reopen it to edit to Tuesday for example, and the screen is already reset to all the defaults, and gives me no indication that I ever set it up . Doesn't throw any errors - why?

it defaults to "daily" "once a day" at midnight no end date, and seemingly no matter what i do it wont save my changes. also, is this screen telling me that it will execute according to these paramters automatically? What if I don't want it to execute at all - I don't see an option available to disable the package?

i'm sure i'm missing something simple - because i verified the scheduler service is running, and i tried it logged in as domain admin - still nothing

 

[NuJoizey]

i should mention that i'm on sql2000, and that i just found where you expand the 'management' folder and click on 'jobs' and it seems to be in there - so then i'm presuming the other screen i referenced above by design does NOT remember your settings - am I right?

 

[AlexCuse]

You schedule a DTS by setting up a job. The job's only purpose can be to run your package.

But you can't schedule a DTS package (to the best of my knowledg) without creating a job. Think of it like windows scheduler, you don't click a setting on your program to run at a certain time, but you can set up a job to run at a certain time that launches your program.

Does this make sense?

Hope this helps,

Alex

[small]----signature below----[/small]
I don't do any programming whatsoever

Ignorance of certain subjects is a great part of wisdom

 

[NuJoizey]

yes it does now. that screen when you right click is confusing though, in server2000 because you expect to see the settings you just made.

I understand now that once a package has been scheduled, it becomes a SQL agent job, and is available under Management>SQL Server Agent > Jobs

as suspected - a novice error!