Zero copy enables organizations to easily connect and use all of their data within the Einstein 1 Platform without needing to move or copy data between platforms. Data 360 enables companies to unify all their enterprise data on Salesforce.
Read the blog
Zero copy integration makes it possible to access data that is sitting in multiple different databases at the same time without having to move, copy, or reformat anything. In addition to making access faster and easier, it cuts down on the expense and risk of errors that’s always incurred when data has to be moved or changed.
Copying data from one database to another is a common practice. Often, this process entails some form of data transformation called extract-transform-load (ETL). It can be a useful and even necessary step in managing enterprise data.
But it has its challenges. Some of the differences between traditional (copying) methods and the zero copy approach are:
| Traditional | Zero Copy | |
|---|---|---|
| Replication | Source data copied from original location to target | Data remains in original location |
| Updates | Data only accurate as of last synchronization point | Data is accessed in real-time |
| Cost | User pays cost of moving and synching data | No data movement cost |
| Regulatory requirements | Harder to keep up with compliance due to more complex governance | User only responsible for source data |
| Errors | Any data movement introduces potential for errors or mistakes | No movement errors |
| Maintenance | Copying and synching creates more complexity | Easier to manage |
Typically, the physical copying of data incurs costs for data transportation, introduces the potential for errors, complicates data governance and management, and creates data-synching time lags.
So how does zero copy integration work? The actual mechanism differs from platform to platform and is different whether you are accessing data from the CDP into the data warehouse or vice versa.
In the following examples, we’ll be using Salesforce Data 360 as the CDP and our partner Snowflake as the data warehouse. Other vendors could be substituted without significantly changing the explanation.
A data warehouse is simply a reliable place to store and access data that is important to the business.
Traditional data warehouses work with highly-structured data in formatted tables, and they tend to be quite slow and complicated. On the other hand, modern data warehouses like Snowflake can handle almost any type of data, process it quickly, and are easier to use. Because they are built on top of cloud platforms like Amazon and Google, they are easier to plug into other systems like CDPs that use the same platforms.
In this case, we are inside our data warehouse and want to access data that is in the CDP. In other words, information is going out from the CDP to the data warehouse. This process is sometimes called data sharing.
The usual steps are:
Behind the scenes, the process creates “virtual tables” that describe the Data 360 data to Snowflake. A virtual table is like a window into data in a database, but instead of copying and storing actual data, a virtual table only contains the structure of the data. It’s a blueprint or pointer to the right place in the CDP to get the data – but the data itself stays in the CDP.
“It is possible to query live data in Salesforce from Snowflake and ensure that changes in the Salesforce objects will be reflected in Snowflake,” explained Salesforce Data 360 product manager Sriram Sethuraman. “This will empower developers and data scientists to build machine learning models and AI-powered applications on top of the Snowflake platform by joining Salesforce and Snowflake data.”
Now we are inside our CDP and would like to access data that is sitting in our data warehouse. This process is sometimes referred to as data federation.
There are a lot of good reasons to do this. Data warehouses like Snowflake and Google BigQuery usually contain a massive amount of data, including transactional data like purchases, and product data. Although not typical “customer” data, such information can be very useful when trying to calculate a customer’s loyalty status or build a recommendation based on details about products they buy.
For example, here’s how you can access data warehouse data in Salesforce Data 360:
The success of cloud-native data warehouses like Snowflake, Databricks, Google BigQuery and Amazon Redshift makes a lot of sense. We’ve seen many customers at least experiment with them and many use them as an integral part of their data architectures. But no data warehouse performs all the functions of a CDP, such as identity management and user-friendly analytics.
Buyers Edge — a leading procurement optimization company in the food service industry — wanted to build a unified customer profile in a CDP while accessing purchase data stored in a data warehouse. Their main goal is to provide better customer insights back to their sales and marketing teams.
Using the zero-copy connection between Data 360 and their warehouse, Buyers Edge gains access to the purchase data it needs to build predictive models, allowing sales and marketing teams to produce better offers, messages and experiences for its prospects and customers.
“With zero-copy technology, accessing customer data stored in Salesforce becomes effortless, eliminating the need for data movement, duplication or reformatting,” said Sean Donahue, chief of staff for the Buyers Edge Platform. “This saves time and resources and removes data silos, harmonizes data for insights and analytics, and empowers businesses with a real-time holistic view of our customers.”
And as companies like Buyers Edge evolve, their requirements will change. That’s why a technology like zero-copy can help them and others build a more flexible data management strategy.
After all, larger enterprises have an average of 976 different applications running their business, and the amount of data created, captured, copied, and consumed is expected to more than double by 2026. Thanks to the power of zero copy data sharing, the looming data explosion will be a lot easier to enjoy.
003960806

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.