Salesforce Summaries – Async SOQL: Big Data Computing for the Salesforce Platform

Share this article...

SalesforceSummaries: a series delivering key insights from Salesforce YouTube videos, to save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.


With the exponential increase of data, it is becoming more and more important to be able to easily and efficiently frequently process millions and billions of records. Since Big Objects has become generally available in the Winter ’18 release, it is opportune to go through Async SOQL; which is the query language used to process big data into the target big objects.

Details: ‘Async SOQL: Big Data Computing for the Salesforce Platform

Presenter: James Ferguson

Time: 21 minutes

Key Terms: Async SOQL, Big Objects


[email protected] — Async SOQL is a new feature that Salesforce have created to help bring big data processing into the platform.

[email protected] — The fundamental challenge is that there is more and more data that is being created. You are creating more customers, you are collecting more information about customers and you want to keep the data for longer (for historical trending, for compliance with new regulatory frameworks etc). Consequently, what starts to happen is that the data volumes increase and new sets of tools and techniques are required to manage these large data volumes.

[email protected] — Big data has traditionally been very challenging to manage. It takes dedicated resources and infrastructure to achieve the efficient management of large data volumes and Salesforce are providing this infrastructure at a much lower cost and much more easily.

[email protected] — There is no longer a learning curve of ‘how do I create a map reduce job?’. Although, with an Async SOQL request, that is what one effectively does albeit so much more easily.

[email protected] — There are many use cases of leveraging large data volumes to provide more value to the business. For example, many Salesforce customers are capturing every single customer touch point (extend customer 360), tracking all the changes made in a Salesforce org and also storing historical data for many years (10 years +) and none of this would be feasible without the Salesforce infrastructure to support large data volumes (Salesforce Big Objects and Async SOQL etc) that number into the hundreds of millions of rows.

[email protected] — The simple example for this demo is that we have a standard object — Orders — and a related Salesforce Big object.

[email protected] — Salesforce Big Objects and Async SOQL were built to look like standard Salesforce objects and standard SOQL.

[email protected] — In this demo, there are 10 million Order records:

And there are over a billion records (the ‘three comma club’) in the custom Big Object:

However, despite this large number of records, navigating to the different Orders and related records in the UI is flawless. This is because the related Big Object (Big Order Items) has been designed to support synchronous queries.

[email protected] — To be able to process a billion records, you cannot use regular SOQL as you’ll reach a time out. Nor can you use batch Apex as it is limited to 50 million records.

[email protected] — However, you can use Async SOQL to process a billion records and more.

[email protected] — Login to Workbench and select ‘Async SOQL Query’:

Now use the following Async SOQL:

[email protected] — Because this is an asynchronous process (it’ll take about 15–20 minutes to process a billion + records) and so instead of just firing it, you need to specify a target object to return the results to.

[email protected] — So create a custom object and map the alias fields from the aforementioned async SOQL query to the fields of that custom object (the target object).

This query will be essentially turned into a map reduce job and the result set will be used to create new records of the target object.

[email protected] — However, if you were to run this again, duplicate records would be created and so you can use the ‘Upsert’ operation type instead.

[email protected] — For another example, let’s us this Async SOQL to group by year and month:

In order to do an Upsert operation for this, you can assign target values to fields:

The aggregation result works very fast:

  1. @20.00 — Big Objects is now generally available (GA) and the Trailhead ‘Big Objects Basics’ is a fantastic place to start to learn about this feature.

Add Comment