SQL Server Integration Services
I am trying to edit an SSIS package due to a change in the schema of one of the source tables. When I open the package in Visual Studio, I see the exclamation mark on the object but before I can make change or go to edit anything in the package, I hear the "dumphhh" sound that indicates an error. There is no dialogue box but the program is now locked up. Then after 10 - 20 seconds the program closes.
How am i supposed to add the new column to the data source metadata if I can't edit the package
This sounds like an error with Visual Studio and/or the package. Can you roll back to an earlier version of the package file and see if you can reproduce the error
Also, do you have this problem with any other packages
Are there any related events in the Event Log
Looks like it must have been a Visual Studio quirky problem. After rebooting again this morning, it let me update the metadata to match the data source. Just curious, how do you roll back a package to an earlier version I've never done that before. As long as you can do it without opening the package, that might have worked too.
csi_hugh wrote:
Just curious, how do you roll back a package to an earlier version I've never done that before. As long as you can do it without opening the package, that might have worked too.
Visual Studio integrates nicely with source control providers like VSS and TFS, and this integration works for SSIS projects just as it does for more "traditional" dev projects like VB and C#. This is where you would get "rollback" capabilities; it's not built into SSIS natively.
You can also simply copy and rename your project folder periodically, to maintain a "rolling snapshot" of packages if you don't have a source control repository handy. It's a kludge, but can still save you sometimes...
Just know that using SSIS in a source control environment *can* cause problems. The XML is not easily "diff-able" and as such sometimes versions get corrupt. Just something to consider. I know people use it regularly without problems though, too.
I had one client using a 3rd party source control system (sorry - cannot remember the name, but it was not Subversion) that regularly corrupted the DTSX files because it wasn't handling them as Unicode correctly.
FWIW, I have had hundreds of packages in TFS for months and have never had issues with corruption.