Hmm. That's odd. Never seen that. And the error message indicates it thinks you don't have the proper version to use a RAW destination component in a data flow. Can you try creating a simple data flow and write data to a RAW destination? Let's make sure you can use that component when you design the package in BIDS.

Can you also try right clicking on the project node and choosing Properties, then changing Run64BitRuntime to False? (or at least to opposite of whatever it is right now)

This feature does wonders for visualizing time spent. But the PipelineComponentTime log event is an out-of-the-box way to figure out how much time is being spent in each data flow component. So you might also try logging that as a workaround to this BIDS Helper issue.

Thank you for your quick reply. Doing a little further research, turns out that I didn't have integration services Windows service installed. After I installed it, I was able to get a run fine by switching the Run64BitRuntime to False. The tool is fantastic!!!!! Great job!

After further testing, looks like I found another issue. I am seeing proper numbers on different trials time executing my tests with, however when I right-click on the data flow task to do show the performance component breakdown, I only get zeros for the duration even though it is executing...

I found what the problem was. I was using a for Loop container to execute a data flow multiple times however the data flow itself ran usually in less than one second in each iteration. That's why was only getting zeros... Sorry for the false alarm.