July 12, 2013 at 1:42 pm
When setting up a new SQL Server 2008 R2 is there any advantage to installing SSIS on a separate server to offload CPU and Memory from the SQL Server? I'm thinking that SSIS service doesn't do much other than manage the packages and monitor the execution of them and the actual ETL SSIS jobs where ever they get run against is where all the processing takes place. But my developers think otherwise. Please advise
Thanks
July 15, 2013 at 12:59 am
Mike Gray-474150 (7/12/2013)
When setting up a new SQL Server 2008 R2 is there any advantage to installing SSIS on a separate server to offload CPU and Memory from the SQL Server? I'm thinking that SSIS service doesn't do much other than manage the packages and monitor the execution of them and the actual ETL SSIS jobs where ever they get run against is where all the processing takes place. But my developers think otherwise. Please adviseThanks
SSIS itself (the service that is) indeed doesn't do a lot. It stores packages and it monitors execution. That's it. If you want to offload SSIS, you need to install SQL Server as well in order to have SQL Server Agent so that packages are actually executed on that server.
So you're right, your developers aren't 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 15, 2013 at 5:49 am
The Integration Services is required to be installed to get some important binaries onto the server but the service doesn't even need to even be running for you to successfully execute an SSIS Package using DTExec.exe. I think your characterization of the service is pretty accurate. Offloading the CPU is all about *where* the package executes, not about the service.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply