I think I found some kind of bug in intellisense layer of the SSIS Scripting Component. I can create a script and Intellisense works perfectly. I then save the script and continue working. If I have to alter the script or add functionality to the script component, Intellisense no longer functions. This happens in both a scripting task and scripting component. To replicate this bug, create a script component, Add some rows to transform. Note, the ROW. will work fine. Save and close the script. Make some changes to the SSIS application. Open the Script component, and add another row for read or read / write. Notice that the Script component Intellisense no longer works. Under *most* conditions, this would not be an issue, but when most of your data columns have an underscore, and SSIS removes underscores and renames columns, it gets to be a pain to work. The only way around the issue that I have found is to create a NEW script component, copy and paste the code and make any changes as Intellisense works in the NEW component. However, if you have to change the component again, Intellisense stops working! Regards, John

You may get additional assistance at the following forum: SQL Server Tools General You can also report a bug at Connect: https://connect.microsoft.com/SQLServer Kalman Toth, SQL Server & BI Training; SQL 2008 GRAND SLAM

Please post a bug at Connect, and post back here with a link to that report. Talk to me now on

https://connect.microsoft.com/SQLServer/feedback/details/667426/intellisense-bug-in-scripting-component Here's the link to the bug report.