August 26, 2010 at 9:08 am
I am troubleshooting a Data Flow task within a massive package of many control flow tasks.
Logging to text file is on and works when running the whole package from BIDS, but I need to see the logging for the Data Flow when using "Execute task" to just run that section. It doesn't seem to bother with the logging when you do this though.
Any ideas?
August 26, 2010 at 5:22 pm
I think that you will have to setup package logging.
From SQL Server 2005 Books Online (November 2008)
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/extran9/html/3c74bba9-02b7-4bf5-bad5-19278b680730.htm
CEWII
August 27, 2010 at 1:33 am
Thanks for the link (didn't work but I think I found the equivalent article in my own BOL.
I AM already setting up logging on the package. But I am not executing the package, does 1 task within the package - and it doesn't want to log it separately. That's really helpful for my troubleshooting/benchmarking before I go live! I don't want to run the whole package!!!!!
Seriously killing me. I've tried a separate log setup just for that particular data flow task and it doesn't create it when I right click execute task.
Also I read that you can view the tab "Log Events" during runtime and it will show all events that would normally be passed to the log files. Oh looky! Its empty and doesn't work!
Anyone? Please!!
August 27, 2010 at 5:30 am
Disable all the other tasks and run the whole package.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 27, 2010 at 5:47 am
I could do that, but surely there is a better method? I have tons of control flow tasks and containers and precedence constraints based on variable values (so it will not get to the data flow unless I undo them due to steps being disabled). I'd rather just get that section logged. If you can't do such a thing - poor show ms!
August 27, 2010 at 10:25 am
Da-Zeros answer is good. If you have a big package zoom out, select everything in the package, and then click disable, the re-zoom, and enable the one you want. Not elegant, but it saves disabling one by one.
CEWII
August 27, 2010 at 10:33 am
Yes but i'm pretty sure any precedence constraints requiring an expression to be met will not be met and therefore it will not move to the only enabled task (will recheck but im sure ive had that before)
August 28, 2010 at 2:43 am
Shark Energy (8/27/2010)
Yes but i'm pretty sure any precedence constraints requiring an expression to be met will not be met and therefore it will not move to the only enabled task (will recheck but im sure ive had that before)
I think SSIS will ignore the precedence constraints as the other tasks are disabled. But I'm not 100% sure. This calls for ... an experiment! (or the A-team)
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 29, 2010 at 8:33 am
Let me know how that test goes BA Zero 😉 - I'm not in front of a SQL server until Tuesday now so no chance to test myself
September 1, 2010 at 7:58 am
Well, I did a small test and it appears that you are right. SSIS will not execute the task if the precedence constraint is not met, even if the previous task is disabled.
Maybe temporarily delete the precedence constraint, disable all other tasks and run the package?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 1, 2010 at 8:03 am
I think that may well be the only option! (other than building my own logging functionality - yuck!)
Cheers
Viewing 11 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply