The Short Answer
The old rule was, "to analyze data, first copy it." Zero Copy eliminates this assumption in many cases: you can query a table residing in an external data warehouse without moving it. This is a real capability, but it trades one type of cost for another. Instead of storage and pipeline costs, you incur computational costs and dependency on source availability.
The decision is correct when treated like any architectural decision: based on usage requirements, not on trends.
Four Decisive Parameters
| Parameter | Leans Towards Zero Copy | Leans Towards Ingestion |
|---|---|---|
| Freshness | Requires the absolute latest data always | Scheduled batches are sufficient |
| Performance | Analysis and segmentation, tolerance for seconds | Real-time operations, consistent response time |
| Volume and Frequency | Large volume, few queries | Medium volume, many queries |
| Governance | Source maintains strong policies | Full control over the copy is required |
This table also explains why most organizations arrive at a hybrid approach: operational streams are ingested, while heavy analytical streams remain in place.
Responsibilities Remaining for the Team Even with Zero Copy
Virtual access eliminates the pipeline, not the work. You still need: schema mapping to the common model, deciding on identification keys for profile unification, handling schema changes at the source, and monitoring availability. Renaming a column in the external warehouse will break a virtual view just as it breaks an ETL.
Therefore, the agreement with the data team that maintains the source is part of the implementation: advance notice of schema changes, a known maintenance window, and an agreed-upon query budget.
Effective Hybrid Patterns
Summary In, Detail Out - Bring summarized values for each customer into the unification layer, leaving detailed records in the warehouse for on-demand access. This is the most common and usually the most cost-effective pattern.
Hot Window, Cold Archive - The last 12-24 months are copied in for performance, and older history remains accessible virtually.
Virtual First, Copy On Sight - Start with virtual access, measure actual usage frequency, and only copy what is proven to be frequently needed. This is an efficient way to avoid copying data that no one will ever query.
The connection between this decision and the division of responsibilities between systems is detailed in Data 360 vs. CRM Data and Source of Truth in an Organization.
Scenario: Financial Company with 400 Million Rows
A financial services company wanted customer segmentation based on seven years of transaction history – approximately 400 million rows in a cloud data warehouse. The original plan was full ingestion into the unification layer.
The pilot changed the decision. It was measured that the actual segmentations relied on only three calculations – monthly average, 90-day trend, and activity classification – all of which could be computed within the warehouse itself. Instead of transferring 400 million rows, three summarized columns per customer, updated daily, were transferred, while the detail remained virtually accessible for ad-hoc investigation.
What was decided here was not "virtual vs. copy" but rather the level of granularity: the correct question was the resolution at which the data was actually needed. Once answered, the copying question became trivial.
Common Risks and Preventive Actions
| Risk | How it appears in practice | Preventive Action |
|---|---|---|
| Unexpected compute cost | Broad queries at high frequency | Measure in pilot and agree upfront |
| Dependency on source availability | Warehouse outage brings down segmentation | Fallback or hot window copied |
| Schema changes | Views break without warning | Change agreement and schema monitoring |
| Undefined permissions | Broader exposure than at the source | Query identity and written exposure policy |
| Incorrect granularity | Transferring detail that no one uses | Determine resolution before method |
How to Measure Success
| Area | What to Measure | Check Frequency |
|---|---|---|
| Performance | Response time for key segmentation queries | Monthly |
| Cost | Compute and traffic cost per Use Case | Monthly |
| Stability | Query failures and source availability | Weekly |
| Value | Segmentations and actions actually created | Quarterly |
The choice of a mix between virtual access and ingestion is made within the framework of Integrations and Data Services.
Checklist for Zero Copy Decision
- ☐ Concrete Use Cases defined, not "general capability"
- ☐ Freshness requirement determined for each Use Case
- ☐ Actual required data resolution checked
- ☐ Query frequency and scan volume estimated
- ☐ Schema change agreement exists with the source owner
- ☐ Query identity and exposure policy defined
- ☐ Hybrid pattern considered before a binary decision
- ☐ Fallback plan exists for source outage
- ☐ Measured pilot before expansion
- ☐ Owner for cost monitoring and periodic review
Professional Resources
- Salesforce Data 360 — https://www.salesforce.com/data/
- Salesforce Data 360 Architecture — https://architect.salesforce.com/docs/architect/fundamentals/guide/data-360-architecture.html
- HPI Pro – Integrations and Data — https://hpi.pro/integrations-data