Before today I have only been fiddling about in with new SQL Server Data Tools Integration Services projects, without any problems what so ever. I’ve seen demos done without any problems what so ever.
And now that I finally get to grind some data with the new tool, it rears its ugly head, for just about every five minutes. I can’t seem to do any, even simple, tasks without Visual Studio hanging/locking up on me. Most of the times I need to kill the process and re-open the project. I do, occasionally, get the kind popup message that Visual Studio is busy. DUH!
It’s not like I’m doing any fancy stuff, at all… Observe CPU load as I do a rename of a sequence container:
In my previous experience with SSIS, I’ve often been able to go ’round problems like these by deleting the, in this case an Excel Source, component and the add the component again. While trying to do so, I deleted the flow between the Excel Source and the Derived Column task. This simple procedure took several hours, and resulted in this message:
I really hope Microsoft deals with this, and soon… Five breakdowns within the hour is not very productive.
Vote at MS Connect: https://connect.microsoft.com/SQLServer/feedback/details/743111/ssis-data-tools-locking-up-hang
In fact there was a Cumulative Update 1 at the time of writing, but there doesn’t seem to be a fix intended for this issue. The update was brought to my attention by Bill Fellows (blog|twitter) as I was ranting about it on twitter using the #SSISHELP hashtag.