Best practice SQL Server 2012 Agent for SSIS/ETL Server

  • Hi there,

    to distribute my resource usage I would like to install a server with the only purpose to run the SSIS packages.

    The new server will have enough network throughput to the first server so the databases would stay on the first server (for all layers).

    To schedule the packages I would still like to use the SQL Server Agent. However this usually comes together with a SQL Server DB installation, as it uses the msdb (and the SSIS DB if you use the project-modell).

    Possibility 1:

    I can install the database service as well and reduce the memory limit of this service to a minimum as only used for the Agent.

    Possiblity 2:

    Use the agent from server one that is just starting the packages on the new server using the new server resources.

    Can you suggest any of this possilbilies or recommend annother one?

    Cheers,

    Chris

  • Am I suggesting something totally absurd?

Viewing 2 posts - 1 through 1 (of 1 total)

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