Skip to main content

SOQL with Big Objects

SOQL with Big Objects

You can query the fields in a big object’s index using a subset of standard SOQL commands.
Build an index query starting from the first field defined in the index, without gaps between the first and last field in the query. You can use =, <, >, <=, or >=, or IN on the last field in your query. Any prior fields in your query can only use the = operator. The !=, LIKE, NOT IN, EXCLUDES, and INCLUDES operators are not valid in any query.
You can include the system fields CreatedById, CreatedDate, and SystemModstamp in queries. To retrieve a list of results, do not use the Id field in a query. Including Id in a query returns only results that have an empty ID (000000000000000 or 000000000000000AAA).

The following queries assume that you have a table in which the index is defined by LastName__c, FirstName__c, and PhoneNumber__c.
This query specifies all three fields in the index. In this case, the filter on PhoneNumber__c can be a range.
SELECT LastName__c, FirstName__c, PhoneNumber__c
FROM Phone_Book__b
WHERE LastName__c='Kelly' AND FirstName__c='Charlie' AND PhoneNumber__c='2155555555'
===============
This query specifies only the first two fields in the index. In this case, the filter on FirstName__c can be a range.
SELECT LastName__c, FirstName__c, PhoneNumber__c
FROM Phone_Book__b
WHERE LastName__c='Kelly' AND FirstName__c='Charlie' 


==================


This query specifies only the first field in the index. The filter on LastName__c can be a range.


SELECT LastName__c, FirstName__c, PhoneNumber__c
FROM Phone_Book__b
WHERE LastName__c='Kelly'


========================


This query doesn’t work because of a gap in the query where FirstName__c is required.


SELECT LastName__c, FirstName__c, PhoneNumber__c
FROM Phone_Book__b
WHERE LastName__c='Kelly' AND PhoneNumber__c='2155555555'


=================


These restrictions do not apply to Async SOQL queries against big objects.
Labels:

Comments

Post a Comment

Popular posts from this blog

ASYNC SOQL - with Big Objects

Async SOQL Async SOQL is a method for running SOQL queries when you can’t wait for immediate results. These queries are run in the background over Salesforce big object data. Async SOQL provides a convenient way to query large amounts of data stored in Salesforce. Async SOQL is implemented as a RESTful API that enables you to run queries in the familiar syntax of SOQL. Because of its asynchronous operation, you can subset, join, and create more complex queries and not be subject to timeout limits. This situation is ideal when you have millions or billions of records and need more performant processing than is possible using synchronous SOQL. The results of each query are deposited into an object you specify, which can be a standard object, custom object, or big object. The limit for Async SOQL queries is one concurrent query at a time. Async SOQL Versus SOQL SOQL and Async SOQL provide many of the same capabilities. So when would you use an Async SOQL query instead of s...
Post a Comment
Read more

Big Objects - Introduction

Big Objects A big object stores and manages massive amounts of data on the Salesforce platform. You can archive data from other objects or bring massive datasets from outside systems into a big object to get a full view of your customers. Clients and external systems use a standard set of APIs to access big object data. A big object provides consistent performance, whether you have 1 million records, 100 million, or even 1 billion. This scale gives a big object its power and defines its features. There are two types of big objects. Standard big objects —Objects defined by Salesforce and included in Salesforce products.  FieldHistoryArchive  is a standard big object that stores data as part of the Field Audit Trail product. Standard big objects are available out of the box and cannot be customized. Custom big objects —New objects that you create to store information unique to your org. Custom big objects extend the functionality that Lightning Platform provides. For ...
Post a Comment
Read more