I've built an SSIS package in SSDT 2012. The package was running successfully until I made a change to a script task.
The task, written in C#, uses an OLE-DB connection to open an Excel workbook and load cell values from each worksheet into separate DataTables. The table data is then stored in SQL Server.
I was opening and closing the connection for each sheet. I then decided to try to make the code more efficient by only opening the .xls file once, looping over the sheets, and only closing it after all sheets had been loaded.
I rebuilt the package. Now, when I run it, SSIS reaches this script task (the last in the package) and hangs, displaying the yellow arrow indicating that it is validating the task:
Any break point that I set in the script code is never reached. (Oddly, if I stop running the package, open the script in VSTA, remove all breakpoints in the C# code, and then save the task, the package designer still shows a red circle, which
I though indicated that the task contains breakpoints.)
These seems like bugs in SSIS/SSDT. What would cause the relocation of some script code to hang the validation process like this?
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.