Salesforce Sandboxes

The development and testing environment within Salesforce is termed as Salesforce Sandbox. The sandbox copy of Salesforce is provisioned with all code, data, and configuration.

 Salesforce Sandbox is not a separate version of the organization, instead, it is just a replica of the original one. Any change in the organization will not be automatically reflected in Salesforce Sandbox.

 A snapshot of the production environment on the date on which it is created is known as Salesforce Sandbox.

The Sandbox environment is created for several purposes like for training, development, testing, and others, even without affecting data and configuration in the Salesforce production instance.

Sandbox Types:

Developer Sandbox:

A Developer sandbox is intended for development and testing in an isolated environment. A Developer Sandbox includes a copy of your production org’s configuration (metadata).

Points to remember:

1)Storage limit is 200MB.

2)Refreshing limits is once per day.

Developer Pro Sandbox:

A Developer Pro sandbox is intended for development and testing in an isolated environment and can host larger data sets than a Developer sandbox. 

A Developer Pro sandbox includes a copy of your production org’s configuration (metadata). Use a Developer Pro sandbox to handle more development and quality assurance tasks and for integration testing or user training.

Points to remember:

1)Refresh limit is once per day.

2)Storage limit is of Max 1GB.

Partial Copy Sandbox:

A Partial Copy sandbox is intended to be used as a testing environment. This environment includes a copy of your production org’s configuration (metadata) and a sample of your production org’s data as defined by a sandbox template. 

Use a Partial Copy sandbox for quality assurance tasks such as user acceptance testing, integration testing, and training.

Points to remember:

1)You can refresh a Partial Data sandbox 5 days after you created or last refreshed it

2) If you delete a Partial Data sandbox within those 5 days, you need to wait until after the 5 day period, from the date of last refresh or creation, to replace it.

3)Storage limit is of Max 5GB and and maximum 10,000 record per selected object..

Full Copy Sandbox:

A Full sandbox is intended to be used as a testing environment. Only Full sandboxes support performance testing, load testing, and staging. Full sandboxes are a replica of your production org, including all data, such as object records and attachments, and metadata.

When you create a Full sandbox, you also have to decide how much field tracking history and Chatter activity to include.

The default is to omit field tracking, but you can include up to 180 days of field tracking. If you track field history for many objects in your production org, specify fewer days to avoid generating an excessive amount of data.

Points to remember:

1)You can refresh a Full sandbox 29 days after you created or last refreshed it.

2) If you delete a Full sandbox within those 29 days, you need to wait until after the 29 day period, from the date of last refresh or creation, to replace it.

3)Storage limits are Same like prod Sandbox.