DWHPro Insights

Stop Comparing Teradata, Snowflake, and Databricks. Start Asking These Questions Instead.

By Roland Wenzlofsky ·

Stop Comparing Teradata, Snowflake, and Databricks. Start Asking These Questions Instead.
comp

A vendor-neutral look at the architectural trade-offs that actually matter

I have spent over 20 years building and optimising enterprise data warehouses, mostly on Teradata, and increasingly on Snowflake and Databricks. What I have observed repeatedly is that platform selection decisions are driven by slide decks, analyst quadrants, and licensing pressure — not by the architectural questions that determine whether the platform will actually work for a given organisation.

Comparing the two cloud platforms? Our Snowflake vs Databricks decision guide covers workload fit, complete cost components and a practical evaluation checklist.

This article is not a feature comparison. It is a list of questions I would ask if I were the person who has to sign the purchase order — and live with the consequences for the next five to ten years.

If you want the side-by-side view first, read the Teradata vs Snowflake comparison, then come back to these questions.


The storage-compute separation: do you actually benefit?

Traditional Teradata block-storage deployments couple AMP compute and storage more closely; VantageCloud Lake also supports independent compute and object storage. Compare the actual deployment and working-set access rather than treating one topology as universal.

This sounds compelling in every vendor presentation. The question I would ask first is brutally simple: what does my workload profile actually look like?

If the organisation runs a steady, predictable analytical workload eighteen hours a day — which is typical in banking, insurance, and telecom — the storage-compute separation buys less than the slide deck suggests. You are paying for compute that is already running. Elasticity does have value for intra-day peaks — scaling from four nodes to sixteen during the month-end close, then back to four — but even that value depends on how pronounced and frequent those peaks actually are. Most enterprises I have worked with dramatically overestimate their peak-to-trough ratio.


The cold cache problem: a cost nobody puts on the slide

Both Snowflake and Databricks rely on local SSD caching to bridge the latency gap between their compute nodes and the remote object storage where data permanently resides. The mechanism is conceptually similar: when a query fetches data from remote storage, that data is cached locally on NVMe SSDs so subsequent queries avoid the network round-trip.

There is a critical difference between the two implementations. Snowflake caches data in its original columnar micro-partition format. Databricks Photon transcodes the data into a different columnar format optimised for SIMD vectorised processing. The Databricks cache is not just the same data stored closer to the CPU — it is the data reorganised for how the Photon engine consumes it.

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

In both cases, the cache is volatile. Suspend a Snowflake virtual warehouse, and the cache is gone. Terminate a Databricks cluster, and the cache is gone. This creates a question that belongs in every TCO analysis but rarely appears there: what is the cost of a cold start, measured in business terms?

If the morning reporting window opens at 06:00 and the warehouse was suspended overnight, how long will it take for dashboards to respond at an acceptable speed? What does it cost to keep the warehouse running all night just to keep the cache warm? For Databricks specifically, how much of the Photon transcoding overhead is paid on every cold start? In fairness, modern partition pruning on both platforms means the cold-cache penalty applies only to the working set, not the entire dataset — but even a pruned working set of several hundred gigabytes still takes meaningful time to re-cache over a network.

To be fair, Databricks offers mitigations: cluster pools pre-allocate instances so the virtual machines are already running when a job starts, and serverless compute shifts lifecycle management to Databricks itself. These reduce the time to cold start, but they do not eliminate the underlying constraint — the cache is still cold, and the data still needs to be fetched and transcoded before queries run at full speed.

Cold-cache latency and cost depend on storage, cache layers, compute lifecycle and the working set on each platform. Traditional local block storage and Lake object storage differ. Measure cold and warm runs; no platform is categorically immune to cache misses.


Photon and the hybrid execution model: how much of your workload actually benefits?

Photon uses a native vectorized engine for supported operations. JVM execution has tradeoffs but is not inherently incapable of SIMD; implementation, generated code, memory and workload determine performance.

Photon’s native vectorized engine can accelerate supported operations, but native code is not universally faster and JVM systems can use vectorization. No reproducible 2–8x comparison is supplied here; benchmark the supported workload.

Unsupported Photon operations can fall back to other execution paths. The boundary and cost depend on the operator and release; inspect the actual plan rather than assuming every remaining operation falls back.

The question I would ask is: what percentage of my current workload uses functionality that Photon does not support? If the ETL pipelines are full of custom transformations — and in my experience, most enterprise pipelines are — then the Photon performance numbers are irrelevant for those workloads. You are buying a sports car that can only be driven on certain roads.

It is worth noting that Databricks has improved this situation. Python UDFs now use Apache Arrow serialisation for the handoff between Photon and the JVM, which significantly reduces the serialisation penalty compared to earlier versions. The gap is narrowing. But the core architectural point remains: supported native SQL often avoids UDF handoff overhead, but relative performance is workload-dependent, and organisations should audit their pipeline complexity before assuming Photon benchmarks apply to their reality.

The follow-up: What is the roadmap for closing the Photon coverage gap? If Databricks plans to support UDFs natively within two years, that changes the calculus. If not, the organisation must plan for a permanent two-tier performance reality within the same platform.


Result caching: an underappreciated differentiator

Snowflake can reuse persisted query results when its eligibility conditions hold, including relevant data and query-context requirements. Reuse is not guaranteed for every query or every user, and cached-result latency is not literally zero.

Eligible repeated queries can avoid warehouse execution, but permissions, context, data changes and cache rules govern reuse. Measure hit rates in the actual BI workload.

Databricks SQL supports result caching as well as data caching. Cache eligibility, persistence and scope depend on compute type and configuration. Compare these documented mechanisms with Snowflake result reuse rather than assuming every Databricks query must execute again.

Teradata handles this differently again. There is no built-in result cache in the Snowflake sense, but the combination of FSG cache (which keeps recently accessed data blocks in RAM on each AMP) and the lack of network latency to storage means that repeated queries against the same data are already fast by design.

Result reuse can materially affect repeated-query performance on both Snowflake and Databricks SQL. Compare eligibility and measured hit rates instead of assuming an exclusive structural advantage.


Teradata in this comparison: why are you actually leaving?

This is the question I would honestly ask myself before spending a single euro on migration planning.

Teradata’s current deployment choices include Lake independent compute and object storage. Evaluate the architecture actually proposed, not only traditional on-premises AMP-local storage.

The compelling reasons to leave are real, but they are specific: the licensing model is unsustainable, the organisation needs elasticity it genuinely cannot get, or it needs capabilities that Teradata does not offer natively. And those capabilities are not trivial — native JSON and semi-structured data querying without ETL, zero-copy data sharing with external partners, Python and ML model execution inside the compute engine, streaming ingestion as a first-class citizen, and an open storage format that prevents permanent vendor lock-in at the data layer. These are genuine architectural advantages of the cloud platforms, not marketing fluff, and for some organisations, they are the deciding factor.

The storage/compute tradeoff depends on deployment, cache behavior and workload. It is not an inherent limitation or advantage shared by every Teradata configuration.

If the answer is primarily “licensing cost,” then the honest follow-up is whether the total cost of ownership after migration — including the migration itself, the re-engineering of ETL, the re-training of teams, and the operational costs of managing cache behaviour, cluster sizing, and performance tuning in a fundamentally different architecture — is actually lower.


The meta-question

If I were sitting across the table from any of these three vendors, the final question I would ask is this:

Show me a reference customer in my industry, at my scale, who migrated from Teradata and achieved the promised TCO reduction after twenty-four months in production — not a proof of concept, not a sandbox, but a full production migration including the cost of the migration itself.

In my experience, that reference is extremely difficult to produce. Not because the platforms are bad — all three are technically excellent in their respective design spaces — but because most large-scale migrations are still in progress, or have quietly exceeded their budgets.

The right platform is the one whose architectural trade-offs align with your actual workload, usage patterns, and your organisational capability to operate it. That answer is different for every organisation, and no vendor slide deck will give it to you.


Roland Wenzlofsky is the founder of DWHPro, a Vienna-based enterprise data warehousing consultancy. He is a Teradata Certified Master with over twenty years of experience across European banking, insurance, and telecom, and the author of “Teradata Query Performance Tuning.” DWHPro provides vendor-neutral advice across Teradata, Snowflake, and Databricks.

Planning a Teradata-to-Snowflake migration?

Review the assessment, conversion, reconciliation and cutover work needed for a controlled transition.

Explore migration services

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Follow DWHPro in Google to see our articles more often in Search.

Leave a Comment

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Protected by Security by CleanTalk and CleanTalk Anti-Spam