Schneider Electric GIS Tech Support

Design versions and their stored displays do not get removed when a design is posted. I created the following sql to generate sdeversion statements that I can then run from the command line to remove the design versions. However, I don't know how I'm going to delete all the extra stored displays. Anyone have any ideas?

Thanks,
Duane Pfeiffer


[i]use tpud_gis
go

SELECT 'sdeversion -o delete -V '+owner+'.'+name + ' -u sde -p <passwd> -N'
FROM sde.sde.SDE_versions
where name in (
SELECT '_DN' + CAST(process.MM_WMS_DESIGN.ID AS VARCHAR) AS ver_name
FROM process.MM_WMS_DESIGN INNER JOIN
process.MM_WMS_WORK_REQUEST ON process.MM_WMS_DESIGN.WORK_REQUEST_ID = process.MM_WMS_WORK_REQUEST.ID
WHERE (process.MM_WMS_WORK_REQUEST.HIDDEN = 1)
)[/i]

You could do a similar thing except you want to delete the sd's entry in MM_STORED_DISPLAYS table. The username will always be __DESIGNER__ and I believe the Name should follow the same convention as your Designer database versions. It looks like you've already got the hard part figured out.

Our geodatabase is running on Oracle 10g. I modified your sql accordingly and ran it. Only one version was found. So, I am just curious if this problem is version specific? We are on ArcFM 9.2.1

I'm using 9.2 SP3. Maybe something changed in 9.2.1. I don't know.

in our custom night program (batch reconcile and compress) we call the ArcFM Orphan Version Cleanup method and it gets rid of those design (and session) versions that don't get cleaned up after a normal post.

I haven't looked at orphaned stored displays, however, thanks. We will look for them and if they exist add a script to clean them up when running our maintenance program.

Do you need a stored display for each design, if so what is their main benefit for you? I have contemplated moving to the no stored display method for designs. If you had none you would not need to delete them. We have 2600 or so stored displays and they take some time (comparatively) to open with a straight sql query. Also the BRP (ArcFM Geodatabase Manager) takes care of stored displays upon posting for us.

we only need the stored displays in designs because we have graphics that are part or the design...as of yet, we haven't been persisting the graphics in a feature class...though I suppose this would eliminate the need for the SD's.