I have noticed a strange behaviour when running some of my packages with dtexec. The packages use EventHandlers to log information to a database using the Execute SQL Task with the query stored in a variable. This variable is further part of the package configuration, so that I can change the query without changing the package itself. Now, this all works fine, until I made a typo in the query causing the syntax to be invalid, ie changing SELECT to SELCET. Now, one would expect the package to fail, and it does, if I run it through the debugger in Visual Studio, but when I run it using dtexec it just hangs and I have to kill the process using the Task Manager.
Peculiarly, I tried doing the same thing with a task that was not contained in an EventHandler, and then the package fails as expected, both when running it in the debugger and using dtexec. This is not a major problem, but what I am afraid of is that one day the database server will be down and cause an error in the Execute SQL Task in the EventHandler, causing dtexec to hang indefinitely. Has anyone else had problems like these?
Regards,
Lars
That's a really interesting observation Lars. I'd certainly be very worried about this happening as well. It might be worth logging as a bug.
I've certainly noticed dtexec appearing to hang but have never managed to track down why. Perhaps this was the reason.
-Jamie
|||I finally managed to track down the problem. It is described here: http://msdn2.microsoft.com/en-us/library/system.diagnostics.process.standardoutput.aspx and it is the deadlock that arises when reading both standard input and standard error after eachoter. In other words, this was related to my poor .NET skills and not a problem within SSIS.
Regards,
Lars
No comments:
Post a Comment