The QuerySurge database retains all of your regularly executed Test Suites by default (Design-Time execution runs are different – only the most recent is retained). This means that not only are the comparison results stored, but the all results data for each query in each QueryPair are stored as well. Disk space can be used up relatively quickly on your QuerySurge database server, depending on the style of testing employed and the amount of storage available to the QuerySurge database. QuerySurge therefore provides Database Management tools in order to deal with the accumulation of data.
Data Management Options
Three Options: DELETE, ARCHIVE, EXPORT
Three database management options are available. All of them operate at the QuerySurge Scenario level. It is important to be aware that these options apply only to your results data, not to any testing assets (i.e., QueryPairs, Suites, Scenarios are unaffected by these options).
- Delete – Deletes all the data associated with the Scenario, including the result data returned during Scenario execution as well as the high-level summary results.
Important: This is a hard delete. If this option is used, the deleted data cannot be recovered.
- Archive – Produces a .sql file containing all the results returned to QuerySurge during Scenario execution, and deletes the underlying tables containing the results data. High-level test results are not deleted, however. The resulting .sql file for the Scenario can be archived and used to restore the data to the system at a later date using the Restore Utility option.
Note: Archive files should be moved off of the QuerySurge application server to long-term storage as soon as possible. This both recovers disk space and protects your files.Note: The Restore Utility reads archive files from the /../backups/ directory on the QuerySurge application server. To restore from an archive, the archive file must be copied back to the backups directory prior to executing a Restore operation, if it has been moved to long-term storage.
- Export – Produces a .sql file containing all the results returned to QuerySurge during Scenario execution. No data is deleted from QuerySurge.
Note: This option does not recover any disk space for you, because no deletion occurs. The purpose of the Export option is simply to provide a file representation of your results data.
ARCHIVE AND EXPORT FILE LOCATIONS
- Zipped .sql files produce during Archiving or Exporting are written to the “backups” folder on the QuerySurge application server.
- On Microsoft Windows, the default installation location is:
- On Linux, the default installation location is:
Note: All zipped output files are stored on the QuerySurge application server. QuerySurge stores the files locally on the QuerySurge application server to avoid pushing large files over the network. However, it does mean that you may consume significant disk space on the QuerySurge application server by Exporting or Archiving. These files should therefore be moved to long-term file storage as soon as is feasible.
ARCHIVING, EXPORTING OR DELETING
You can access the Data Management tools by logging into QuerySurge as an Administrator, and navigating to the Administrative View. In the left nav tree, click on Scenario Data Management under Data Storage.
To initiate the Archive, Export or Delete process, either Shift-click on a range of Scenarios or Cntrl-click on individual Scenarios to select them.
Then use the Archive, Delete or Export buttons to Archive, Delete or Export the selected Scenarios:
Important: To safeguard your QuerySurge data, back up the database regularly. Your only protection against data loss is a regular backup schedule. In the case of a severe outage your only possibility of recovery is based on a recent backup. See this Knowledge Base article for backup procedures.
If you fill up your disk
If you run out of disk space on your database disk, your QuerySurge instance will likely become unstable, and it may stop functioning. Depending on circumstances, you may lose data, possibly irrecoverably. Do not try to resolve this issue yourself; get in touch with QuerySurge Support for a resolution.
Important: If this situation occurs, stop using QuerySurge immediately. Do not attempt to restart QuerySurge services. Do not attempt to run executions and other tasks. Contact QuerySurge Support immediately.
Important: Under no circumstances should you move or delete any files in your QuerySurge install directory or in QuerySurge's database directory. Any actions that you take on your own may result in irrecoverable data loss.