all groups > sql server dts > august 2005 >
You're in the

sql server dts

group:

dts schedules



dts schedules Bill Orova
8/11/2005 11:01:48 AM
sql server dts:

Hi all,
This one has me stumped,
how do you verify the scheduling or run time of an existing dts package

Bill

Re: dts schedules Mnemonic
8/11/2005 12:30:07 PM
Edit the package using DST Designer. Go into package properties, and
look at the Logging tab. Enable logging, if not enabled (and write log
to local server). If it's already enabled, then exit DTS designer and
in Enterprise manager right click on DTS job and select Package logs.
Then you will at least know when it ran, and that should help you track
back to the job.

Note: the job has to run at least once after logging is enable for it
to have a log to view....
Re: dts schedules Mnemonic
8/11/2005 12:33:47 PM
Edit the package using DTS Designer. Go into package properties, and
look at the Logging tab. It not already, place a checkmark to enable
logging (and write log to local server). If it is already enabled, then
you can exit the DTS designer. In enterprise manager, right click on
DTS job and select Package logs. You will then be able to see a log of
when the dts ran, how long each step took, and error messages. What's
really cool is that it'll separate the logs by the version of the
package.

Then you will at least know when it ran, and that should help you track

back to the job.

Note: the job has to run at least once after logging is enable for it
to have a log to view....
Re: dts schedules Mnemonic
8/11/2005 12:43:35 PM
P.S. When selecting what server to write the log to, "localserver" may
not always be the best option, as "localserver" is a relative term.
Best to specify the Server name to ensure it's written to the right
place.
Re: dts schedules Rick Gittins
8/11/2005 3:07:00 PM
In Enterprise Manager go into Management => SQL Server Agent => Jobs. Here
you can see all the jobs that are scheduled, when the will run, last run,
next run, ...

Rick

[quoted text, click to view]

Re: dts schedules Mnemonic
8/12/2005 7:43:30 AM
Sure that works, but unforunately only if the job name matches the dts
name. In an environment with hundreds of scheduled multi step jobs, it
can be quite hard to associate which DTS is buried in which job.

Logging will tell you which date/time it runs, and also will help you
catch any time a package is run by an external force (I.E. A user, exec
or DTSRun commands)
Re: dts schedules Bill Orova
8/12/2005 8:34:54 AM
Mnemonic
thank you very much


AddThis Social Bookmark Button