I need to scale out my SSIS environment. I do not have the resources for another SQL Server license and my SQL Server is reaching max load during execution of SSIS packages (yes, everything has been optimized and I'm using best practices to squeeze as much performance out as possible). Based on what I've read, I can create a remote server with Integration Services only installed without incurring another SQL Server license. However, here's where my question comes in...
If I create a remote server with Integration services only installed, I want the "work" to be done on that server (yes, I realize that I will incur I/O on the SQL Server when writing/reading from databases). The stumbling block seems to be that most folks can't do this because they are dependant on the SQL Agent for job scheduling, and that is dependant on SQL Server. If I put a scheduling agent from my enterprise scheduler on my new SSIS-only server, will the work then be located on that new SSIS-only server?
Is this a valid architecture?