domainverion table question

Bryan

It seems the domainversion in our database is taking up quite a bit of space. I am looking for any insight on what this table contains (it appears to be bsv storage). Also, is it possible to remove some of the entries from the table?

If this is a bsv storage area it makes sense to keep the most recent few entries but I would like to remove those that are no longer applicable if possible.

Thanks

tford

In the Standard menu there is an submenu option to delete Business Spaces.

Bryan

I have already removed all business spaces that I do not need on the server. I am looking for a insight into if it is possible to clear out some of the old data relating to existing business spaces from the domainversions table. The blob field is storing a lot of data for each bsv that is uploaded. I would like to clear some of the old data because over the life of this server it will just keep getting bigger and bigger and effecting performance on the server.

Thanks

aware_support

Don't try to modify this table directly - you can seriously stuff up the system. One of the reasons that this table is large is if you have lots of OBSOLETE or working versions for your current business space. Get rid of the unnecessary versions from the Configuration Tool.

Bryan

148 rows in the table and 7 obsolete business space (minor) versions prior to clean up

Removed the 7 obsolete business space versions.

148 rows in the table

Is this what I should expect?

aware_support

Strange. There should be roughly as many rows in the table as the versions you see in the Config. Tool. Well, if you create a backup of the table, you can try removing the rows

RLJB

we have ₂₃,096 records in our DOMAINVERSIONS table, taking up around 670MB.

We certainly don't have that many versions of business spaces.

Can we delete some? If so, how do we know which ones?

ACDC

One thing I have noticed in the past, if you delete business spaces in the config tool they are not deleted in the database. (Mysql)

This problem should be resolved as it could cause mayhem if something does go wrong. ..I have been there -- not nice.

RLJB

Bryan - did you succeed in deleting anything out of DOMAINVERSIONS table? And did it cause any other problems?

(we now have 26,000 rows in that table with 848 MB)

Bryan

I ended up with a manual clean-up process on all but the latest 3 (to be safe) business space publications.

For example if you had the following in the domainversions table. I would only delete 1.0 & 1.1

BASTestDomainBUSINESSSPACE --- 1.0
BASTestDomainBUSINESSSPACE --- 1.1
BASTestDomainBUSINESSSPACE --- 1.2
BASTestDomainBUSINESSSPACE --- 1.3
BASTestDomainBUSINESSSPACE --- 1.4

Deleting from both the domainversion and the dvhistories tables to ensure consistency

delete FROM domainversions where dname='BASTestDomainBUSINESSSPACE' and versionstr='1.0';
delete FROM domainversions where dname='BASTestDomainBUSINESSSPACE' and versionstr='1.1';

delete FROM dvhistories where dname='BASTestDomainBUSINESSSPACE' and versionstr='1.0';
delete FROM dvhistories where dname='BASTestDomainBUSINESSSPACE' and versionstr='1.1';

I did not come up with a completely elegant solution on the script side so I manually put my list together with the help of Excel.

All in all this process was completed with no ill effects.