💃 Mo data, mo problems 🕺

Good morning, Salesforce Nerds! Data is everywhere these days. It’s one of the key elements of any application! 🔑 

I mean think about it. 🤔 What do your users do all day?

Create data. All day. Every day. 🌅🌙 

In the application you helped design & build! 💪 

As usual … we need to be careful! 🫣 

We can avoid MANY problems down the line by planning for Large Data Volume (LDV) in our orgs.

Today let’s cover the main contributors to the issues that arise from LDV! 💯 

Agenda for today includes

• Common causes of LDV

• Daily Principle

• All the Memes

Common causes of LDV

Today we will discuss -

💃 What is LDV 🕺

💃 What to watch for 🕺

💃 How to address it 🕺

Job Board | 💃 Click Here 🕺

Socials | 💃 Linkedin | Instagram | Twitter!🕺

📈 What is LDV

The official Salesforce definition is:

So, basically, we’re talking about Salesforce org’s that have:

🟡 10k+ Users or

🟡 10m+ records or

🟡 100+ GB total record storage

Is this you? 🫵 Will it be? 🤔 

What are some things to keep a pulse on so we can be confident our solution will stand up the scale? 🏗️ 

👀 What to watch for

There are a few things you can proactively look into to see if your org needs a little LDV attention:

❌ Object Size

Yes, I know this is rather obvious. 🙄 

Check the volume or data size of the SObject in Setup. ✔️ 

There are no published numbers to validate against. 🤷 But, if you’re seeing numbers like in the previous section, you’ll want to start mitigating.

❌ Record Ownership

In Salesforce, every record must have an owner. ☁️ 

This can be a single user or a queue/group of users. Salesforce uses this design for security/visibility purposes. 👀 

Usually this is fine, but issues arise when 10k or more records share the same owner.

So, if you have a placeholder Account record where you place a bunch of Contacts … be warned. This can come back to bite you! 🐍 

❌ Data Skew

This means we’ve associated too many child records to a parent record. ⚖️ 

It’s a similar problem compared to the ownership skew above, but here you’ll start to see more row locking. 🔐 

This happens when an update is happening to a child record a lock is placed on the parent record during the transaction to maintain data integrity. 💥 

If you have thousands of child records rolling up under a parent start to make a plan now … 👍️ 

🛠️ How to address it

✅ Query Plan

The Developer Console contains a tool to review & evaluate the performance of queries against LDV’s. 🎭️ 

The tool helps you to optimize queries using selective filters to increase performance! 📈 

Run your most important queries through it and see if you’re running the best query you can! ⏩️ 

✅ Skinny tables

If you’ve got an SObject with millions of records in it that your users need to regularly need to report off of or see in a list view them this may be what you need. 🤩 

These are kind of like denormalized, flat files that combine frequently used fields and remove joins from query execution at the database level. 🎚️ 

This will take a Case submitted to the mothership! 🛸 

✅ Custom Indexes

Indexes power queries by providing a method to quickly lookup the requested data. 💪 

Simply put, an index is a pointer to data in a table. They’re very similar to an index in the back of a book. 📑 

If the standard indexed fields just aren’t enough for you then you can also submit a case to Salesforce and get a Custom Index created. ✍️ 

Think ahead though … there are field types you can’t do this one - checkbox, long text, currency, multi-select picklist. ⛔️ 

Daily Principle

and now....Your Daily Memes