Applies to QAComplete 12.13 SaaS, last modified on April 18, 2019

There are several factors that determine how to install and maintain the SQL Server instance hosting QAComplete (ALMComplete) databases (named SoftwarePlanner). Here are just a few of them:

  • The number of users who will be working in QAComplete (ALMComplete) on a given day.

  • The presence of other databases on the servers.

  • Your company network policy.

  • The physical resources upon which the SQL Server instance will reside.

The databases themselves can be maintained differently due to the data they store:

  • The SoftwarePlanner database is the primary database of the application. This database includes all product data, traceability, security permissions, and other settings.

    You should implement a backup strategy that best meets your organizations expectations regarding data loss for this critical database.

  • The SoftwarePlannerWS database stores Performance Logs and Database Logs each time the psWS web service is invoked. A nightly differential backup for this database may be sufficient, but this should be determined by your internal organization. Since this data is historical, quotas and a job could be used to "flush" the data when the database reaches a certain size.

  • The SoftwarePlannerSession database primarily stores end user session specific information that is temporal in nature. It also includes a VersionLogs table and BaseCodes table which rarely change but could be updated in an upgrade.

    Since a majority of the data in this database is temporal, the size of this database remains fairly consistent.

    Typically, you would backup this database each time the main SoftwarePlanner backup is performed, so that in the event of a failure of the system, you have a common restore point for both.

What backup approach to use

Every client, every environment has unique characteristics which can impact what kind of backup strategy you implement. It is difficult to provide a specific detailed set of recommendations that would work in large and small companies throughout the world. Instead, we can point you to the resources which we believe can help you develop best practices for your organization:

Microsoft SQL Server 2008 R2 Best Practices Analyzer

This is a tool that your SQL Server administrator can download and run on the server to analyze how the software is installed and configured, identify differences in the configuration from Microsoft recommendations, and provide options for resolving those differences.

Monitoring and Tuning for Performance

This Technet article provides guidance for tuning an SQL Server performance.

DBCC Commands

This is a list of commands that can be run to check the integrity of various database objects. These can be scheduled by your SQL Server administrator to be executed on a routine basis to ensure the health of your databases.

Backing Up and Restoring Databases in SQL Server

This provides an overview of the different strategies you can implement to ensure your data is protected.

Also, we recommend checking out our Community page, where you may be able to get an idea how other clients have implemented a backup strategy –

SmartBear Community

If, after reviewing the information above, you feel you need additional help, professional guidance and services are available via a third-party consulting group. Please contact our Customer Care team, if you are interested –

https://support.smartbear.com/message/?prod=QAComplete

See Also

On-Premises

Highlight search results