Please refer to the following article: http://www.k2underground.com/blogs/johnny/archive/2008/04/15/deleting-obsolete-process-instances-from-a-k2-net-2003-or-k2-blackpearl-database.aspx

Please not that this is not supported, test in a dev environment and make backups beforehand.

Vernon

Vernon,

Thanks for the link, unfortunately I came across that article and that doesn't apply to the situation here.

I am looking for a way to clear out the _Assembly table as that is the main culprit for sucking up the disk space.

Maybe Archiving will do the trick here:

http://help.k2.com/en/KB000322.aspx

Vernon

I saw that article as well, but this is for the Log database (which is only at 300 megs), the K2Server db is the problem.

I am almost wondering if it would be easier to just delete the databases in development and re-run the config manager to re-create the DBs.

The _assembly represent references, according to theory you can clear it and then the references will be added automatically as they are needed, hence not adding back the obsolete ones. Maybe this will work for you, but once again, make a backup before doing this.

If you opt to delete the databases and re-run the config manager, remember to delete both the K2server and K2serverlog db’s, they need to be in sync.

HTH

Regards

Vernon