December 24, 2008 at 2:49 am
Hi all,
I am in the process of building a new SQL server. I decided that all i needed was the SQL Server and SQL Server Agent services. Intergration Services is not installed. I created my maintenance plans and then thought to myself that they would not run because they are essentially SSIS packages and therefore would require an SSIS engine. I thought i'd let them run anyway to see what happened and they did indeed run.
How does this work?! And, i suppose more importantly, what is the SSIS service actually doing to support package execution if packages, i.e. maintenance plans at least, run without the service?
Many thanks.
James
December 24, 2008 at 5:17 am
When you install the MSSQL database engine, the SSIS execution objects are always installed. This was done to support the maintenance plans and import/export wizards.
The SSIS service does a couple of things. First, it handles verifying the edition of SSIS that is installed. So, if you do not install it and try to run a package that contains objects other than the basic import/export components, you will get an error indicating that you do not have the appropriate edition of SSIS installed.
Next, it handles security for storing and accessing the packages. SSIS uses DCOM to allow access to SSIS packages stored in MSDB or on the file system via Windows integrated security. Take note that it does not have a built in remote execution facility other than the SQL Agent.
There are probably a few things I am leaving out, but I have only had one cup of coffee so far this morning.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply