October 24, 2007 at 7:41 am
If you use any automated method of moving DTS packages you will loose the package layout and annotations seen in the original package in DTS Designer. The package will still work in the same way, but the layout and annotations have been lost.
The only way to keep this information using just MS software is to manually export each package to a structuerd storage file, and manually load it. There aer some third-party products that can export and import DTS packages and keep the layout and annotation details.
The reason this stuff gets lost is that MS have never published the interface to the COM objects that supports these details. DTS Designer in SQL 2000 and 2005 uses a private interface to capture the layout and annotations, but scripts will loose these details. I guess the third-party tools have either worked out how to capture these details from the standard COM object or have written their own export and import processing.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 26, 2007 at 12:14 pm
You were right, applying SP2 made the issue go away. Now I can edit the packages again.
Thanks,
Ed
October 26, 2007 at 12:27 pm
The information here might help
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply