jobs runing on the server

  • hi folks

    i need to find out a way to figure out how many jobs are been pulled out from the server ,

    lets say

    there are server A and server B and a server c

    how can i tell that

    which jobs are been pulled out from server A and server B and going to server C ( ex, lets say raplication jobs, regular backup???)

    any help will be helpful.

    bobby

  • qur7 (3/21/2008)


    hi folks

    i need to find out a way to figure out how many jobs are been pulled out from the server ,

    Please clarify ... Are you trying to figure out how many jobs are run from a server? Are you trying to figure out which jobs and how many originate on one server and talk to a different server?

    Please clearly explain your objective.

    Thanks

  • hi,

    is a matter a fact i need to know both ,

    but for now will be ok with how many jobs runing on a server and going to a particular server

    eg,

    going from server A to going to server B.

    and also will help if can also find out that ..... how many jobs

    originating from server C ( all of the jobs)

    thanx in advance.

    bobby

  • Well, msdb.dbo.sysjobs_view contains all of your job information.

    You're not going to know if a SQL Agent job communicates to another server as a job can basically do anything. You can be calling stored procedures which use linked servers, openquery, openrowset, etc. You can have jobs that run DTS/SSIS packages that talk to another server.

    Bottom line, there is no way to say "show me X jobs that talk to Y server". You'll need to start crawling each job and finding out what they do to determine that.

    Actually, I haven't used it before, but SQL Agent does have the ability to run jobs directly against another server if you set it up for that. Simply look at originating_server under the view at the top of this post.

  • thank you for ur help.

    i will see how it goes and keep u all posted here.

    shahid

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply