Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Salesforce Data Architecture and Management

You're reading from   Salesforce Data Architecture and Management A pragmatic guide for aspiring Salesforce architects and developers to manage, govern, and secure their data effectively

Arrow left icon
Product type Paperback
Published in Jul 2021
Publisher Packt
ISBN-13 9781801073240
Length 376 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Ahsan Zafar Ahsan Zafar
Author Profile Icon Ahsan Zafar
Ahsan Zafar
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Section 1: Data Architecture and Data Management Essentials
2. Chapter 1:Data Architect Roles and Responsibilities FREE CHAPTER 3. Chapter 2: Understanding Salesforce Objects and Data Modeling 4. Chapter 3: Understanding Data Management 5. Section 2: Salesforce Data Governance and Master Data Management
6. Chapter 4: Making Sense of Master Data Management 7. Chapter 5: Implementing Data Governance 8. Chapter 6: Managing Performance 9. Section 3: Large Data Volumes (LDVs) and Data Migrations
10. Chapter 7: Working with Large Volumes of Data 11. Chapter 8: Best Practices for General Data Migration 12. Assessments 13. Other Books You May Enjoy

Large Data Volumes (LDVs)

LDVs in Salesforce don't have a strict formal definition, and if you ask an experienced architect what constitutes an LDV scenario, more than likely the answer you will get will be, It depends. The reason is that you could have an LDV scenario even with a much lower number of records than the general guideline that Salesforce provides. The general guideline is that once you have more than 1 million records in any object, you have an LDV scenario and you may start seeing the implications of LDVs.

Although the number of records is a consideration in determining whether an LDV scenario exists, that is not the only consideration. There could be several other factors that could create an LDV scenario even when the number of records is less than the generally recommended threshold, which is more than 1 million records. These factors include the following:

  • Transaction volume and complexity: This is related to how much data is moving in and out of...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image