This presentation discusses salesforce sandboxes, salesforce sandbox pricing, Salesforce deployment, sandbox best practices and salesforce sandbox refresh policies

1. Flosum
The Definitive Guide to
Salesforce Sandboxes
Flosum

2. Flosum
Content Overview
• Salesforce Sandbox types
• Value Proposition
• Use Cases
• Best Practices
• Pricing & Packaging

3. Flosum
Product Line

4. Flosum
Salesforce Sandbox Product Line
Developer Developer Pro Partial Copy Full
Refresh Interval 1 Day 1 Day 5 Days 29 Days
Includes Setup
Configuration
Yes Yes Yes Yes
Copies Data
Records
No No Yes Yes
Sandbox
Templates/
Sampling
No & No No & No
Yes & Yes (10,000
records/object)
Yes & No (Full Data
Copy)
Sandbox Size
200MB Data
200MB File
1GB (~500K records)
1GB File
5GB (~2.5M records)
File Storage
Dependent on Sample
Match Production for
Data and File

5. Flosum
Understanding the Products
• Refresh Interval
– A refresh is the re-creation of a sandbox. This allows the customer to work in
the salesforce sandbox that was created while we build a new one in the
background. The interval is the amount of time between refreshes.
• Setup Configuration
– This is also referred to as your org metadata. These are custom object
definitions, page layouts, apex classes, permission sets, etc. It is the set of
objects that can be manipulated through the Metadata API
• Data Records
– This is the actual data created by the customer, e.g. an Account or
Opportunity record

6. Flosum
Understanding the Products (cont’d)
• Salesforce Sandbox Templates
– A sandbox template is an artifact that the customer uses to define what data records(e.g.
Account, Custom Object) get copied into the sandbox on a creation or refresh operation.
• Data Sampling
– Sampling is used in a partial copy sandbox to limit the amount of data that is copied. This
ensures the data fits into the sandbox and that the sandbox is created in an optimal
amount of time.
• Developer Sandbox Bundling
– This is the number of Developer Sandboxes that are included with the purchase of a
specific sandbox.
• Storage
– This is the data and file storage included in each sandbox

7. Flosum
Value
Flosum

8. Flosum
Everything from your Production Org in Just One
Click
Each Sandbox Environment includes:
• All features, functionality, user licenses and setup
configuration in the production org
• Additionally, Full Sandbox includes all of the
production org’s data
Sandbox
Environments
Your meta-data and
production data

9. Flosum
With Sandbox, you get All of our Developer
Tools
Each Sandbox Environment includes:
• Visual Force and Apex for Client and Server
side Programming
• Cloud & Desktop IDE
• Configuration Deployment Tools & APIs –
Integrate with your SCM and Dev Tools
Sandbox
Environments
Your meta-data and
production data

10. Flosum
No more Desktop Workspaces or internal Test Infrastructure,
All Sandboxes are in the Salesforce Cloud
Each Sandbox Environment includes:
• Sandbox Refresh
• Release Preview
• Sandbox Org Back-up & Disaster Recovery
• Infrastructure Maintenance & Upgrades
Sandbox
Environments
Your meta-data and
production data

11. Flosum
Use Cases

12. Flosum
Product & Use Case Alignment
Use Case Developer Developer Pro Partial Data Full
Build ✔ ✔ ✔ ✖
QA ✔ ✔ ✔ ✖
Integration Test ✖ ✖ ✔ ✔
Batch Data Test ✖ ✖ ✔ ✔
Training ✖ ✖ ✔ ✔
UAT ✖ ✖ ✔ ✔
Perf/Load Test ✖ ✖ ✖ ✔
Staging ✖ ✖ ✖ ✔

13. Flosum
Products and Use Cases Explained
• Full Sandbox is not an agile environment. They have a 29 day refresh
interval and can take days to create for a large org. This is not ideal for
the Development and QA uses cases that require the ability to change
direction and work on something new fairly quickly.
• The sample data set provided by Partial Copy sandbox is suitable for the
majority of use cases. A good representative set of product data should
be enough to get through functional and end user testing.
• A full data set is only required for Staging, Performance and Scalability
testing

14. Flosum
Best Practices

15. Flosum
Team Setup
• Develop in Isolation
– Not in production
– If possible, not in same dev org as their peers
– If you have to share a dev org, do it on a per project or work item basis
• Teamwork
– Synchronize with peers to leverage each others work
– Stable checkpoints to hand-off between functions (e.g. QA)
• Integrate when complete
– Integrate with peers when development and unit test complete
– Integrate with current production for testing and approvals

16. Flosum
Code Management
• Have a Change/Release Management Process!
– No change management process out of the box
• Integrate with Source Control
• Manage multiple code lines
– You can get more out of your agile environments
• Automate your deployments
– Force.com Migration Tool (Ant Tool)
• Consider Continuous Build Systems

17. Flosum
Release Planning
• Understand our release schedules
– 3 Major Releases, Participate in the Preview Window, and Follow
trust.Salesforce.com
• Are you conservative or aggressive?
– If you are conservative, regression test through the Preview Window and
don’t deploy anything new until after a Major Release
– If you are aggressive, release early and often
• Have a documented Project Plan
– Requirements/User Stories, Test Plans, Release Schedule
• A Release Train for each Project

18. Flosum
Sandbox Environment Management
• Refresh Full Sandbox Staging Environment before Deploying to Prod
– Track the processing time of your full sandbox, so you know how long it takes to create
– Never refresh a Sandbox for Metadata – Use Source Control!
• Activate the refreshed Full Sandbox after verifying the Prod Deployment
– You have 30 days to activate a Sandbox, so take advantage of the ability to have one
waiting
• Have strict User Governance
– Restrict admin capabilities in the production org to a small group that also manage the
release
– Limit user access in developer sandbox (Developers, Testers Only)
• Create a Post Refresh Run-List
– Document repeatable post process tasks such as: data masking, user/profile
modifications, test data loading, turning off scheduled jobs, managing outbound email

19. Flosum
Pricing and Packaging
Flosum

20. Flosum
Salesforce Sandbox Product Line
Developer
Business analysts bui ld
apps with meta-data
• Bundled with Sandbox
Add-On purchases
Developer Pro
Programmers and ful l-time
admins bui ld with meta-data
• 5 % of ACV Add-On to
PE, EE, UE, or PXE
• Includes 5 Developer
Sandboxes
Partial Copy
Fast refresh with sample
production data
• 20 % of ACV Add-On to
EE, UE, or PXE
• Includes 10 Developer
Sandboxes
Full Copy
Al l your meta-data and
production data
• 30 % of ACV Add-On to
EE, UE, or PXE
• Includes 15 Developer
Sandboxes

21. Flosum
Sandbox Edition Bundling
Enterprise Edition
1 Developer
Performance
Edition
1 Full Copy
1 Partial Copy
5 Developer Pro
30 Developer
Unlimited Edition
1 Full Copy
5 Developer Pro
10 Developer

22. Flosum
Flosum