The database of our SF is starting to become a little too big for our liking, and this may result in slower upgrades whenever Thinkwise releases a new version. When we first started using Thinkwise software, we were told it was not necessary to delete any old versions, as one could lose some history in for instance the template code history. I was wondering whether there are any updated best practices or recommendations from Thinkwise on how old project versions and branches can managed.
Page 1 / 1
Hi Thomas,
This is up to the business to decide. Some customers like to store their history in the Software Factory, others rather clean up the version and keep it to a couple of versions in their Software Factory.
We are looking into a solution where we can end the usage of project versions and work with temporal tables. This will eliminate the huge amount of data in the operational data (non-history table) and move all changes to history tables.
For now and the next version, it will stay the same - working with project versions. Maybe you can ask around in your organization to see how far people look back in older project versions to see earlier changes. If for instance, only a few developers end up looking back a version or two, then maybe you can keep 10 inactive project versions; or every release of your end product, cleaning up another few project versions. There isn't really a rule of thumb for this.
You could also make a backup of a Software Factory, archive it, then clean up project version in your operational Software Factory. Hope this helps!
Hi Mark,
Thank you for your quick reply, I am glad to see that you are working on a strucural solution to this! It seems that untill the solution is implemented we will have to do some cleaning up (safely of course using a backup!).
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.