SSDT (SSIS) Bug – Marking a parameter as sensitive causes various Task Editors to close unexpectedly without error


Though I’d share details of another SQL Server Data Tools (SSDT) bug to hopefully save others the time I wasted trying to figure out what was going on.

Details

SSDT Version: November 2012 Update

Project Type: SQL Server Integration Services (SSIS)

Setting the Sensitive flag of package parameters to True causes various Task Editors to close down unexpectedly without error when trying to access properties associated with Variables.

Steps to Reproduce

1. Create a new Integration Services Project

SNAGHTMLb389bb

2. Open the default Package

3. Click on the Parameters tab

4. Add a new parameter and set its Sensitive property to True

image

FTP Task

5. Add a FTP Task to the package

6. Open the FTP Task Editor by double clicking on the FTP Task

7. Select the File Transfer page

8. Set the IsLocalPathVariable property of the FTP Task to True

9. Try and select a value in the LocalVariable property field

SNAGHTMLb88e7c

File System Task

10. Add a File System Task to the package

11. Open the File System Task Editor by double clicking on the File System Task

12. Select the General page

13. Set the IsDestinationPathVariable property of the File System Task to True

14. Try and select a value in the DestinationVariable property field

SNAGHTMLc40d5c

BTW, if you set the IsSourcePathVariable property to True and then try and select a value in the SourceVariable field, a dropdown list is displayed showing a list of variables/parameters.  This is the expected.behaviour.

SNAGHTMLc59d6b

Summary

This error occurs on a number of other Tasks and I’m not sure whether this existed prior to the SSDT November 2012 Update as I don’t have a machine without this update to test against.

Microsoft Connect ID: 771677

SQL Server 2012 SP 1 Breaks SQL Server Database Projects


After installing SQL Server 2012 Service Pack 1 you will discover that SQL Server Database Projects can no longer be opened (or created) using SQL Server Data Tools (SSDT).  The error presented when trying to open existing projects is:

Unable to open Database Project

This version of SQL Server Data Tools is not compatible with the database runtime components installed on this computer

ssdt

(BTW, Clicking on the “Learn more…” and “Get the latest version of SQL Server Data Tools…” links at the bottom of the dialog returns “Page not Found” errors.)

To fix this problem you need to install SQL Server Data Tools – November 2012 update.  That said, when you now try and open an existing project/solution, you are advised that the project needs Migrating however no migration wizard is launched and there is no visible way of migrating the project.

To migrate your project you need to Right Click on the Project name and select “Reload Project”.

image

This will launch the “One-way Upgrade wizard” which converts your project into the latest version of SSDT.

SNAGHTML52e6800

Would be nice if SP 1 included the SSDT update and that the migration wizard automatically launched when opening a project.

%d bloggers like this: