| || |
Silk Test Database Size
I think I posted about this before (or something similar). It seems like almost every month our Silk Test Database grows by like 20gb (maybe its ever couple of months, it just seems like its every month). Why?
I would say maybe one new script gets written a month. (maybe).
We do have problems with the (Microsoft SQL Server) Transaction log getting out of control. (it was 90gb today). Our Windows 2012 server started out being 80gb (HD space) , now we have to increase it again up to 200gb because we keep running out of space? I would say over the year and half we have only written maybe 40 scripts.
We have turned off any images being created for runs. We are setting it up to override existing results to keep the results down. (not sure how that would work, if I delete the Silk test results, then what results would Silk Central have?)
Any other ideas for getting this database under control? I don't mind it growing, but is there something we can run to get things back a base point???
Is there steps we should perform on the database every week or month? You can probably tell I don't know Microsoft SQL very well.
Hi tubaloth ,
Silk Test Workbench includes the "Asset Purge" tool for removing old version of assets (e.g. results or tests).
The following link shows how to use this tool:
I would suggest trying the purge tool manually first (via the SIlk Test Workbench UI). If it significantly reduces the size of your data base you can then run the purge tool on regular basic. Note that there is even a command line version of this tool. The documentation can be found here:
Last edited by gecki; 12-16-2014 at 08:21 AM.
With regard to SQL Server, there are ways of reducing the size of the transaction log, these logs only help you if you need to rollback to a previous state.
Do we know what those ways are?
We do purge pretty often now. Even with us telling Silk Test to override results, it seems like Silk Test keeps different versions of the script. I don't think there is a way to tell it to only keep the last 5? (I guess the purge tool does that).
I noticed (or remembered) the Database Maintenance tool. In there I see there is an option to Compact.
Should I use that tool to "shrink" the database?
I'm not sure if that would fix the transaction log problem, but it might make the database smaller, and maybe even free up purged memory???
Any other ideas for getting this database under control? I don't mind it growing, but is there something ,,,,,,,,,,,