February 20, 2002 at 11:54 am
On one of my Development SQL Servers(7.0), I have a job that was created from a DTS package. The DTS package is NOT stored on this box. Under Local Packages it is not there. I have to go to Jobs...(the owner is a User/Login for that Database).
The job runs every night at 12:00am.
I want to know who created this package and from where it is running.
If I look under Process Info. there is a column for HOST, but this only shows "current" activity.
I can stay here at 12:00 and check the Host name --> but I am hoping there is a better solution.
Any ideas ?
February 20, 2002 at 1:10 pm
It could be running from a COM file, a .DTS file. What is the job definition?
Steve Jones
February 20, 2002 at 2:48 pm
Under the Job properties....
Command :
DTSRUN/......bunch of #/letter combination.
February 20, 2002 at 3:08 pm
Unfortunately I don't have a EM here, but that I know is a schedualed package, that for some reason microsoft decided it would be best to encrypt the parameters. I believe it was for the username and password properties not to be seen. What I would suggest is set up Profiler and set it to monitor that Job or at least DTS packages as it may give you more details about what is goind on, then force the job to run whenever and watch.
February 20, 2002 at 3:28 pm
You might try searching for some .DTS files on the server and see if there are any.
Steve Jones
February 21, 2002 at 8:41 am
If I run the job it just says the "Job was invoked by Schedule 89(DTS_0000000001)". That's it. I have no other information.
I think this was a DTS Package created on a Developers box, ran it against my SQL Development Server, which created the job locally.
Now I am stuck with the job and don't know who created it(just have the Login name - which alot of people use --> i know, i have to change this).
Will the profiler give me what I am looking for here ?
I am thinking since I only now have the Job, I am out of luck. Is this the case ???????
February 21, 2002 at 10:39 am
Probably. Profiler will at least tell you if this is doing something on your box. It might be doing something on another SQL box, in which case, you'd have to run profiler against that box to see what happens.
You can always delete it and see if anyone complains.
Steve Jones
February 21, 2002 at 11:03 am
Actually don't delete it, just disable it so it will not run, that way if someone does complain it is no trouble to recover.
February 21, 2002 at 1:53 pm
Will the Process Info. tell me anything ?
I need the Host Name. But if its a Job stored locally I don't think it will show a HOST name when it runs.
???
February 21, 2002 at 2:55 pm
It will if it connects to that server. If it connects to another server, you won't see anything.
Steve Jones
February 21, 2002 at 3:07 pm
you'd think if a Job was stored locally one could see the Job Details.
February 21, 2002 at 4:22 pm
You are confusing this info. The job is the definintion of a command that runs. What is runs is something separate and that could be deleted.
The job is encrypted so that if someone schedules a job, no one can casually determine the parameters. I'm not sure I agree with it, but that's how it is.
If you don't like it, you can manually schedule jobs and call DTSRun with unencrypted parameters.
Steve Jones
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply