How many full Sandboxes can you have in Salesforce?

How Many Full Sandboxes Can You Have in Salesforce?

As a Salesforce administrator, you may be wondering how many full sandboxes you can have in your organization. In this article, we will explore the limits and restrictions of full sandboxes in Salesforce, as well as provide guidance on how to create and manage them.

What is a Full Sandbox?

A full sandbox is a replica of your production org, including all data, such as object records and attachments, and metadata. It is intended to be used as a testing environment, allowing you to test and validate changes before deploying them to your production org.

Limits and Restrictions

There are several limits and restrictions to consider when it comes to full sandboxes in Salesforce:

• Enterprise Edition: In Enterprise Edition, you can have a maximum of 1 Full Sandbox after purchasing a Full Sandbox. You can also create up to 11 Developer Sandboxes.
• Performance Edition: In Performance Edition, you can have a maximum of 1 Full Sandbox, 1 Partial Copy Sandbox, 5 Developer Pro Sandboxes, and 30 Developer Sandboxes.
• Unlimited Edition: In Unlimited Edition, you can have a maximum of 1 Full Sandbox, 5 Developer Pro Sandboxes, and 15 Developer Sandboxes.

Creating a Full Sandbox

To create a full sandbox in Salesforce, follow these steps:

1. From Setup, enter Sandboxes in the Quick Find box, then select Sandboxes.
2. Click New Sandbox.
3. Enter a name (10 characters or fewer) and description for the sandbox.
4. Select the type of sandbox you want.
5. Select the data to include in your Partial Copy or Full sandbox.

Managing Full Sandboxes

Here are some tips for managing your full sandboxes in Salesforce:

• Refresh Interval: Full sandboxes have a refresh interval of 30 days, which means that any changes made to your production org will be reflected in your full sandbox after 30 days.
• Data Storage: Full sandboxes have a data storage limit of 5 GB, which means that you should be mindful of the amount of data you store in your sandbox.
• Metadata: Full sandboxes include all metadata, including custom objects, fields, and pages.

Best Practices

Here are some best practices to keep in mind when working with full sandboxes in Salesforce:

• Use a naming convention: Use a consistent naming convention for your sandboxes to make it easier to identify and manage them.
• Use a description: Use a description for your sandbox to provide context and information about its purpose.
• Test thoroughly: Test your changes thoroughly in your sandbox before deploying them to your production org.
• Monitor data storage: Monitor your data storage usage to ensure that you do not exceed the 5 GB limit.

Conclusion

In conclusion, full sandboxes in Salesforce are an essential tool for testing and validating changes before deploying them to your production org. By understanding the limits and restrictions of full sandboxes, as well as how to create and manage them, you can ensure that you are getting the most out of this powerful feature. Remember to use a consistent naming convention, use a description, test thoroughly, and monitor data storage usage to ensure that your full sandboxes are running smoothly and efficiently.