"Rick Brandt" <rickbrandt2@hotmail.com> wrote in message
news:ZutTg.6319$TV3.3504@newssvr21.news.prodigy.com...
> We have SQL Server 2005 and have installed the "add-in" that allows us to
> edit DTS2000 packages. However there seem to be two areas that were
> available in SQL Server 2000 that are not available in 2005 using the
> add-in.
>
> First off there seems to be no way to access the logging of the DTS2000
> package. In 2000 you just right-clicked and looking at the logs was an
> option right there in the pop-up menu.
>
> Second is that every edit to the DTS2000 package creates a new "version"
> and you end up with a series of the older versions accumulated in the
> package. There seems to be no way to clean up these older versions as
> there was in 2000 where you could just select them and delete them.
>
> This is a problem because we call these DTS2000 packages from SSIS
> packages and they do not automatically execute the newest version when
> there are multiple versions in the package. If we could delete all but
> the newest version then we would not have to edit the SSIS package every
> time we edit the DTS2000 package.
>
> I'm just wondering if there actually is a way to do these things that is
> not obvious to me. We are rebuilding some of our 2000 packages entirely
> in SSIS as we have time, but a couple of these are pretty large packages
> and we might not get around to converting them for a while.
>
> TIA
>
>
>

Darren Green wrote:
> I am not sure if the features are there but in answer to your first
> two points, I woudl just use the tables. I have been doing it this
> way even in DTS proper for some time now.
>
> For the logging, just query the tables sysdtspackagelog,
> sysdtssteplog etc
> To remove old versions, just delete the row from sysdtspackages.
>
> I use a property expression to blank the VersionId property on the
> EXec DTS Package Task, so we always pick up the latest version.