Deleting/Archiving Packages - D-Tools Forum

Andy N · 05-01-2008, 03:49 PM

We have come to a point were our database has a few of, what I consider to be "one time use" packages that were created and the odds are extremely unlikely that they would ever be needed again, thus having the potential to clutter our Package List.

Since I do not see an archive funtion for packages, I am wondering the ramifications of actually deleting the Package from our DB, and if anyone has any tips on an effective way to "slim down" their packages section. Without, of course causing negative ramifications. ie; the one time use package is still in use on a current project. The actual items in the potentially deleted package are obviously still part of the Database, they just would not be in their old package.

Thanks!

**Kevin Mikelonis** · 05-01-2008, 04:51 PM

A key element to always keep in mind about the database to project file relationship and vice versa is that items from the database (packages included) in the project are isolated from the database.

So deleting from the database will not affect existing projects.

Also note that Packages names, descriptions, and content can be changed when adding them to a project WITHOUT creating a new package in the database (this is new for SI5 and I do hope it remains true with SI5.2).

This implications of this enable database managers to keepPackages named in a more 'high level' manner and wehn added to a project, specifics in the name and description of the package may be added.

So I say 'Go ahead-clean it up!'