Remove Obsolete ​.SDB Files

When sessions are merged in a PADD database, it is possible to specify if .SDB if should be considered for deletion too via a file purge option (see MERGE CHANGES in the Administration Command Reference Guide). If file purging is not utilized as part of the merge session operation, obsolete files can be deleted as a separate action via a PML form as described below.

To show the form In Marine Drafting or Hull Design, type in the following in the Command Window:

show !!RemoveObsoleteSDB

The following conditions must be fulfilled:

• User access right must be FREE.

• No other user is connected to the project.

It is also highly recommended that changes in PADD databases are merged first. The fewer sessions there are, the faster the macro will finish.

Click the Find obsolete SDB files button. All 32 directories below %<proj>DRG% are scanned and each .SDB file is checked. Please note that this might take a long time if there are many sessions in the database. All obsolete SDB files are listed. The list shows the name of the obsolete file together with the reason why it is obsolete.

• Missing element - the SHEE no longer exists.

• Replaced - the SHEE element uses another SDB file (new version).

• Not SHEE - the element exists but it is not SHEE.

Right-click in the list to:

• Sort the list.

• Delete individual obsolete .SDB file.

There are three buttons that perform an action for all .SDB files in the list:

• Delete all .SDB files in the list.

• Move all .SDB files in the list to the given directory.

• Export the list to a CSV file.

It is possible to customize the path that is used by the application when moving .SDB files. Set the environment variable SBB_OBSOLETE_SDB_BACKUP to the path of an existing directory. If the variable is not set then Windows variable TEMP is used.