We help IT Professionals succeed at work.
Research Question

Understanding Salesforce Big Objects, from an Oracle perspective

Last Modified: 2020-08-07
We have a home-grown Oracle ERP system and an Oracle Data Warehouse, and now are migrating to Salesforce (and Big Objects).

I am posting this in Oracle community hoping to find someone with an Oracle perspective and maybe knows Salesforce a bit.

My main questions / comments are:
- Big Objects has a limitation of 100 tables, this seems to be terribly limiting (and does not compute to an Oracle person)
          - plus we don't have Big Data, we have little data

- For an ERP with little data, why couldn't a 2nd Salesforce database (org) be set up as the Data Warehouse?
       - All other DW solutions are for Big Data: Azure, AWS, Google Cloud Dataflow, etc.

- if we learned the new ERP in regular SF, we'd just start writing reports out of that (and likely use Einstein Analytics to do so).
      - So the data would flow from Salesforce ERP to Big Objects to Einstein
      - And I'm like, "why not just report out of regular SF?" - we don't have Big Data.

Currently, Oracle ERP flows to an Oracle DW, which is roughly similar to the ERP, just a few changes, it's slightly de-normalized, etc. But if there are 100,000 student records in the ERP, there's 100,000 in the DW, so basically the same.

We use traditional tools to report from the Oracle DW, such as PL/SQL Developer, Business Objects, etc. No dashboards, just list-based reporting, some crosstabs, etc.

The general plan is to use Einstein as the reporting tool, so the data would move from Big Objects to Einstein, meaning we really won't use Big Objects to report from, it's just a place to house Big Data.
Watch Question

Gadsden ConsultingIT Specialist


Well, this is what I found from a buddy who knows Salesforce:

Big Objects is way different from regular Salesforce, although you could use Einstein Analytics for both.

Big Objects is focused on three main areas:
1. Adding 360 degree view (multiple data sets) of a customer (e.g., Student)
2. Audit and tracking (like maybe track who comes on your campus with IoT devices)
3. Historical Archiving

Of course one of its main purposes is for Big Data (billions of rows) and fast retrieval time

It's not a relational data structure, it's denormalized a LOT. For example, you might have Student info in one object that drives all the way down to courses, grades, instructors (and all related tables).

But the biggest thing he emphasized is we need to have an Archive strategy. iow, What's it actually being used for?
IT Specialist
This one is on us!
(Get your first solution completely free - no credit card required)
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.