Microsoft SQL Server Requirements for Salesforce

To store a local copy of the Salesforce data and to perform certain functions, store your Salesforce data in a database. Each Salesforce organization needs a separate database. For example, if you back up two production organizations and one sandbox organization, configure three databases.

The following functions require a database:

  • Object comparisons

  • Record-level restores

  • Restore to the Salesforce cloud

  • Sandbox seeding


  • Microsoft SQL Server

  • Microsoft SQL Servers that use the Always On availability groups feature

  • Azure SQL Server

  • Amazon RDS for SQL Server

Connection Information

The Commvault Salesforce application connects to a database with default options such as connection timeout, host, instance, and so on. If your setup requires additional connection properties, configure the sf_dbConnectionProperties additional setting.


  • You must have a SQL authentication user who has owner permissions, and if the database does not exist, has the dbcreator role.

  • You must be able to access the database from the internal network.

  • For operations that restore data from the Microsoft SQL database, such as record-level restores, the database must be accessible from the Web Server on default port 1433.


    If you are not using the default port, you must open the port that you configured.

Hardware and Software Requirements

  • The Microsoft SQL Server version must be 2008 R2 or higher.

  • The database host must have a minimum of 8 CPUs/processors and 16 GB of memory. We recommend 32 GB of memory.

  • To prevent the database host memory from filling up, set the max server memory limit for the SQL server. For more information, see the Microsoft SQL Server article, Server Memory Server Configuration Options.

  • The database host must have free space that is at a minimum equal to four times the size of the Salesforce used data storage. This amount of free space accounts for the following:

    • Salesforce data change frequency because the database maintains all versions

    • Data used space

    • Additional table size, such as share and history tables

    • Index size

    • Log size

    Additional space is needed for out-of-place restore operations. When you perform an out-of-place restore, the source data is copied, the copy is used for the restore, and then the copy is removed.

    For instructions about checking the storage usage values, see Checking the Values for Salesforce Storage Usage.


Best Practice: To avoid filling the disk with transaction logs during the Salesforce backup, use the SQL Simple Recovery Model.

Salesforce Access Node: System Requirements