Hello,
I have a package which runs several child packages. All works well and everything runs, but when it runs each of the children packages, it opens it, runs it and then it stays open. When the whole thing is done, there are about 25 or so open packages. Should they close after they run? Is there a setting I need to do this?
The point I am in SSIS is that I have gotten a decent feel for creating packages, but everything is still in debug mode. I need to take the next step to learn how to have this stuff run automatically or from a procedure outside the SSIS interface. Does that make any sense? If so, where can I learn about that.
Thanks for the help.
-Gumbatman
When you say the package remains open after execution, you are talking about the package designer window on Visual Studio (BIDS)? If so then don't worry it us not an issue.
When you execute a package in the designer it actually has an entirely different instance loaded for the execution. The debugger uses a special application, dtsdebughost.exe, to host the running package. This then hooks into the designer to give you progress information, colours and other messages.
The real execution package has closed you just see the static designer artefact, the open package window. Compare this with execution without debugging, (try Ctrl+F5 is it inside VS) which uses DTExec, a regular execution host.
|||DarrenSQLIS,
Thanks so much for the information. I didn't know about (or understand) that when running it in the BIDS.
-Gumbatman
No comments:
Post a Comment