Home Forums SQL Server 2012 SQL 2012 - General SSMS connection to SSIS with packages on remote MSDB server - is that even remotely possible? RE: SSMS connection to SSIS with packages on remote MSDB server - is that even remotely possible?

  • Evil Kraig F (3/3/2013)


    Unlike Jason, I work in a shop where we have a dedicated SSIS box. There are benefits, but they're not readily apparently. However, it's also not a scalable solution like you're looking for.

    Basically there's three reasons we run our SSIS on a separate box (well, vm instance, but same thing to us). First is memory control. SSIS runs outside the server cache and they'll compete. We keep a small engine on the same box simply for configuration controls and SQL Agent but that's it. Second is security. SQL Agent requires a large amount of rediculous control to create test jobs (to test network security for filepaths, doublehops, etc) and share them amongst a team (group ownership isn't allowed for a job yet).

    ...

    We actually run a separate instance for SSIS - it's just not like what the OP requested.

    I prefer the SSIS server for the same reasons you just laid out.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events