Post reply

Creating job to run SSIS package Remotely

  • January 7, 2014 at 3:16 pm

    #284244

    Hi,

    I have a question.

    I have a ssis package in the DW environment. How can I run this package in the production environment by creating the job and run remotely.

  • January 7, 2014 at 3:29 pm

    #1678256

    I'm confused as to the problem. Are you trying to initiate the package from one server, but have it run locally on another?

    Basically... you don't. You need to use a tool like psexec.exe to send a local command over to the other server to initiate the package.

    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
    Twitter: @AnyWayDBA

  • January 8, 2014 at 12:15 am

    #1678320

    ramana3327 (1/7/2014)

    Hi,

    I have a question.

    I have a ssis package in the DW environment. How can I run this package in the production environment by creating the job and run remotely.

    If you want a package to run in the production environment (what's the difference with the DW env?), you'll need to schedule it on the production environment. A package is not executed where it is stored, but where it is called.

    (unless you use the 2012 project deployment model. Package will always be executed in their catalog)

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • January 9, 2014 at 1:06 pm

    #1678952

    HI

    This link will give you most of the instructions of executing a SQL job remotely.

    http://judepieries.blogspot.co.nz/2013/09/how-to-execute-sql-job-remotely.html

    Hope this is what you are looking for.

    Thanks

    Jude

  • January 10, 2014 at 12:08 pm

    #1679277

    Thank you.

  • January 10, 2014 at 3:27 pm

    #1679336

    jude.pieries (1/9/2014)

    HI

    This link will give you most of the instructions of executing a SQL job remotely.

    http://judepieries.blogspot.co.nz/2013/09/how-to-execute-sql-job-remotely.html

    Hope this is what you are looking for.

    Thanks

    Jude

    Please note, that's remote execution of a job, not a SSIS package. Just as simple would be to send over a sp_StartJob proc command on the foreign server.

    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
    Twitter: @AnyWayDBA

  • March 27, 2015 at 6:12 pm

    #1787079

    Let me make sure I'm following this: I can set up an app server to house SSIS, point SSIS to store packages on the actual db server in msdb. But to execute that package from a SQL Server job, I need to have SQL Server Agent on the app server? Doesn't that mean that I need an install of the db engine on the app server? Which is a generally recognized no-no?

  • March 30, 2015 at 2:36 am

    #1787233

    tcuddington (3/27/2015)

    Let me make sure I'm following this: I can set up an app server to house SSIS, point SSIS to store packages on the actual db server in msdb. But to execute that package from a SQL Server job, I need to have SQL Server Agent on the app server? Doesn't that mean that I need an install of the db engine on the app server? Which is a generally recognized no-no?

    There are other ways to schedule SSIS packages. You don't need to use SQL Server Agent.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

Viewing 8 posts - 1 through 7 (of 7 total)

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