Decoding Sandbox Creation: How Long Does a Partial Sandbox Take in Salesforce?
Fast answer first. Then use the tabs or video for more detail.
- Watch the video explanation below for a faster overview.
- Game mechanics may change with updates or patches.
- Use this block to get the short answer without scrolling the whole page.
- Read the FAQ section if the article has one.
- Use the table of contents to jump straight to the detailed section you need.
- Watch the video first, then skim the article for specifics.
So, you’re diving into the world of Salesforce sandboxes, and the burning question is: How long does it take to create a partial sandbox in Salesforce? The answer, as with most things in the cloud, is “it depends,” but let’s unravel the mystery.
In general, when you refresh or create a new sandbox, the process may complete within a few hours, but it can also take several days or more. The timeframe fluctuates depending on several factors, primarily the complexity and size of your Salesforce org. A good understanding of these factors is crucial for planning your development and testing cycles effectively.
Factors Influencing Partial Sandbox Creation Time
Several elements contribute to the duration of a partial sandbox creation or refresh. Recognizing these factors allows you to better anticipate the timeframe and potentially optimize your org for faster sandbox operations.
Level of Customization and Configuration
The more customized your Salesforce org is, the longer the sandbox creation will take. This includes:
- Number of Custom Objects: More objects mean more data and metadata to copy.
- Custom Code (Apex, Visualforce, Lightning Components): The complexity and amount of custom code need to be copied and validated.
- Workflows, Validation Rules, and Processes: These automation rules require replication and testing within the sandbox environment.
- Integrations with External Systems: The sandbox needs to be configured to mimic these connections, which can add time.
Organization Size and Data Volume
The sheer size of your Salesforce org, particularly the amount of data it holds, directly impacts sandbox creation time. Consider these points:
- Data Storage Usage: The closer you are to your storage limits, the longer the process will take. Partial Sandboxes have a data storage limit, so it is important to respect the 5 GB limit of storage space and a 10,000 record maximum per selected object
- Number of Records in Key Objects: Large objects, even with data sampling in partial sandboxes, still require significant processing.
- File Storage Usage: Although Partial Copy sandboxes allow for only 5 GB of file storage, copying the file and documents will increase the overall time.
Server Load and Salesforce Infrastructure
Salesforce’s infrastructure plays a role. If the servers are under heavy load, sandbox creation might be slower. This is usually outside of your control, but it’s a factor to consider.
What Exactly Happens During Sandbox Creation?
Understanding the behind-the-scenes process can help you appreciate the time involved. The sandbox creation involves:
- Environment Provisioning: Salesforce allocates resources for your new sandbox environment.
- Metadata Copying: All your configuration settings, custom code, and schema definitions are copied from your production org.
- Data Sampling (for Partial Sandboxes): A subset of your production data is copied based on the templates you define.
- Post-Copy Script Execution: Any scripts you’ve configured to run after the copy are executed, often to mask data or adjust settings.
- Environment Activation: The sandbox is made available for use after all the copying and scripting is complete.
Monitoring Sandbox Creation Progress
Salesforce provides ways to track the progress of your sandbox creation:
- Setup Menu: Navigate to Setup > Sandboxes to see the status of your sandbox.
- Email Notifications: You’ll receive an email when the sandbox creation starts and when it completes. The email will notify you that your sandbox has completed copying.
Tips to Potentially Speed Up Sandbox Creation
While you can’t control everything, here are some strategies to potentially reduce sandbox creation time:
- Optimize Data Sampling: Carefully select the data you need in your partial sandbox. Avoid copying unnecessary data.
- Clean Up Unused Metadata: Remove old or unused custom objects, fields, and code to reduce the amount of data that needs to be copied.
- Minimize Post-Copy Scripts: If possible, reduce the complexity and execution time of your post-copy scripts.
- Refresh During Off-Peak Hours: Consider scheduling sandbox refreshes during times when Salesforce servers might be less busy (e.g., weekends or late at night).
Frequently Asked Questions (FAQs)
Here are some common questions regarding partial sandboxes in Salesforce:
1. What is the difference between a developer sandbox and a partial 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. A Partial Copy sandbox is intended to be used as a testing environment. Partial Copy sandboxes also let you include a subset of your organization’s data, for example, 10,000 account records.
2. What are the limitations of a partial sandbox in Salesforce?
Partial Copy sandboxes have a 5 GB of files and a 5 GB of data storage limit. Developer Pro sandboxes have a 1 GB of files and a 1 GB of data storage limit. Developer sandboxes have a 200 MB of files and a 200 MB of data storage limit. Full sandboxes have the same storage limit as your production organization. It is important to respect the 5 GB limit of storage space and a 10,000 record maximum per selected object.
3. How often can I refresh a partial sandbox in Salesforce?
You can refresh a Partial Copy sandbox every 5 days. This frequent refresh interval is ideal for ongoing testing and development activities.
4. What happens when you refresh a partial sandbox Salesforce?
The sandbox refresh procedure creates a new org, copies the metadata and data from the source org, then deletes the old org after activation. This ensures you have a fresh copy of your configurations and data. A sandbox refresh deletes and recreates the sandbox as a copy of the production org. This process reverses any manual access changes you made.
5. How do I refresh a partial sandbox in Salesforce?
From Setup, enter Sandboxes in the Quick Find box, then select Sandboxes. A list of your sandboxes displays. Sandboxes that you can refresh have a Refresh link next to their name. Next to the name of the sandbox you want to refresh, click Refresh.
6. How many records are in a partial sandbox?
While Full sandboxes have the same storage limits as your production organization, Partial Copy sandboxes allow for only 5 GB of storage space and a 10,000 record maximum per selected object.
7. Why is my sandbox slow?
Keep in mind that your sandbox is designed to test code, and not to load tests. Keep the number of products and locales to a minimum. For example, if you’re storing more than one thousand products in a sandbox, performance may be impacted.
8. What happens to users after a sandbox refresh?
This process reverses any manual access changes you made. If you created sandbox-only users, then they no longer exist. Other users’ profile and permissions revert to their values in the production org. A sandbox refresh deletes and recreates the sandbox as a copy of the production org.
9. What is the sandbox lifecycle in Salesforce?
A sandbox is a copy of your organization in a separate environment that you can use for a variety of purposes, such as testing and training. Sandboxes are completely isolated from your Salesforce production organization. The operations you perform in your sandboxes don’t affect your Salesforce production organization.
10. Can we recover a deleted sandbox in Salesforce?
It is not possible to recover a deleted or refreshed sandbox clone. Restoring cloned sandboxes is not supported. Sandboxes deleted by the unused sandbox sweeper will not be restored.
11. What is the difference between sandbox and playground in Salesforce?
The Salesforce Developer and Sandbox Environments have a common goal – testing, training, and development. But their roles differ. While the former is perfect for making custom apps, Sandbox is a playground to effect the needed changes. This is done without compromising the original work. In order to explore the value of “play” within the learning process check out GamesLearningSociety.org, an organization devoted to researching how games-based learning can improve education outcomes.
12. How many sandboxes can be created in Salesforce?
An Enterprise organization has a limit of 10 Developer Sandboxes and 1 Full sandbox after purchasing a Full sandbox. They can create up to: 11 Developer sandboxes.
13. How do I clean up my sandbox in Salesforce?
Deleting a sandbox will completely delete your sandbox and all its contents. A sandbox can only be deleted if its refresh interval has passed. If you do not see the delete option, you will need to wait until the refresh interval has passed in order to delete the sandbox.
14. What are the two types of Sandboxes?
In fact, there are 4 different Sandbox types and each of them have different levels of functions and features: Developer Sandbox, Developer Pro Sandbox, Partial Copy Sandbox, and Full Sandbox.
15. What is the difference between sandbox and partial sandbox?
A partial sandbox environment copies over a sample of your Production environment’s data, while a full sandbox is a literal clone of your Production environment. This means all your data from your Prod environment (people data, content, permissions, etc.) gets carried over to the sandbox, and vice versa.
In Conclusion
While there’s no single answer to “How long does a partial sandbox take in Salesforce?”, understanding the influencing factors and best practices can help you plan and manage your sandbox environment effectively. By optimizing your org and leveraging Salesforce’s monitoring tools, you can minimize downtime and ensure a smooth development and testing experience. Remember that effective sandbox management is an ongoing process, and with a little attention, you can keep your sandboxes running smoothly.