SQL Server Developer Center >
SQL Server Forums
>
SQL Server Integration Services
>
Where is SSIS running?
Where is SSIS running?
On my local machine, SQL Server Integration Services is in a Stopped state. I see this in SQL Server Configuration Manager.
Given this, if I run a package on my machine, then where is it running?
Answers
- The SSIS service doesn't have anything to do with execution of packages*. No matter where you execute the package, DTEXEC.EXE or a similar executable is invoked.
* Note - the service is used for checkpoint restarts on SSIS packages, if checkpoints are being used.
Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer- Marked As Answer byDoolinDalton Monday, November 02, 2009 9:08 PM
All Replies
- Guessing you are running it in BIDS which has it's own internal components to execute the package. Otherwise without SSIS services you would need to execute the package with DTEXEC
Ted Krueger Blog on lessthandot.com @onpnt on twitter - The SSIS service doesn't have anything to do with execution of packages*. No matter where you execute the package, DTEXEC.EXE or a similar executable is invoked.
* Note - the service is used for checkpoint restarts on SSIS packages, if checkpoints are being used.
Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer- Marked As Answer byDoolinDalton Monday, November 02, 2009 9:08 PM
- Cool. I did not know that and though services were required to run at all times while executing packages (no matter the content).
Thanks Phil
Ted Krueger Blog on lessthandot.com @onpnt on twitter - Just to add...
The only function that SSIS provides (AFAIK) is caching of components that get used during execution - the supposition being that any packages that use them in the future will be able to instantiate them quicker. Given that no-one (least of all MSFT) has published stats on the advantage of doing this I assume that the advantage is ridiculously negligible if indeed there is an advantage at all.
Phil,
I wasn't aware that the SSIS service gets used for checkpoint restarts. Can you elaborate?
-Jamie
http://sqlblog.com/blogs/jamie_thomson/ | http://jamiethomson.spaces.live.com/ | @jamiet - @Jamie - http://blogs.msdn.com/blogdoezequiel/archive/2009/04/06/why-do-you-need-ssis-service.aspx
Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer - @Phil, @Jamie - just confirmed with the SSIS team that the SSIS service is not involved in checkpoints - that post is incorrect.
John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com @Phil, @Jamie - just confirmed with the SSIS team that the SSIS service is not involved in checkpoints - that post is incorrect.
John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com
Hmm, ask them please what does the service do, and can we get a BOL article on that? I'll send Doug a note in the mean time...
Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer- This thread stuck with me sense my initial readings on SSIS years ago left far too much open.
I think it could be chopped up to BOL again missleading or just not being critical enough over the internals.
Bottom line all that is given is...
(http://technet.microsoft.com/en-us/library/cc966389.aspx)
"The SSIS service is installed when you select the option to install SQL Server Integration Services and its purpose is to enable the management of SSIS packages"
Management can mean far too many things. I'd like to see Phil's request
"Hmm, ask them please what does the service do, and can we get a BOL article on that? I'll send Doug a note in the mean time..."
get accomplished if anyone has further contact into it with the team.
I did a ton of reading on the checkpoint topic and found nothing either on that front for services handling it. Who's right? I don't think anyone is wrong over my incorrect statement of, "Otherwise without SSIS services you would need to execute the package with DTEXEC"
Ted Krueger Blog on lessthandot.com @onpnt on twitter - Here you go, Ted. http://www.ssistalk.com/2009/11/04/ssis-what-does-the-ssis-service-actually-do-anyway/
The content on that post of mine came after talking with the product group.
Turns out checkpoint restarts of failed SSIS packages is not part of the service's responsibility. The MSDN blog page I linked to above was incorrect and has since been pulled.
Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer- Edited byPhil BrammerMVP, ModeratorWednesday, November 04, 2009 4:24 PMClarification on checkpoints
yeah, worrying that the guy who wrote that works for Microsoft on the PFE SQL Server team (whatever that is). We all make mistakes but ... that one was completely out of left field!!
Turns out checkpoint restarts of failed SSIS packages is not part of the service's responsibility. The MSDN blog page I linked to above was incorrect and has since been pulled.
http://sqlblog.com/blogs/jamie_thomson/ | http://jamiethomson.spaces.live.com/ | @jamiet
