StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Databases
  5. Oracle vs Snowflake

Oracle vs Snowflake

OverviewDecisionsComparisonAlternatives

Overview

Oracle
Oracle
Stacks2.6K
Followers1.8K
Votes113
Snowflake
Snowflake
Stacks1.2K
Followers1.2K
Votes27

Oracle vs Snowflake: What are the differences?

Differences between Oracle and Snowflake

  1. Query Language: Oracle uses SQL as its query language, while Snowflake uses a variant of SQL called SQL-like language. Although both languages are similar, Snowflake's SQL-like language incorporates some unique syntax and features specific to its platform.

  2. Architecture: Oracle follows a traditional on-premises or single-node architecture, where a single database server handles all data processing tasks. On the other hand, Snowflake utilizes a cloud-based architecture, which includes separate compute and storage layers. This architecture allows Snowflake to deliver elastic scalability and separation of compute and storage, resulting in better performance and cost optimization.

  3. Scalability: Oracle's scalability is limited to the capacity of its hardware and infrastructure, requiring manual adjustments to handle increased workloads. In contrast, Snowflake provides automatic and on-demand scalability by decoupling compute and storage resources. Snowflake can seamlessly scale up or down based on workload requirements without any manual intervention.

  4. Data Sharing: Oracle allows data sharing through traditional methods such as exports, imports, and replication, requiring significant effort to maintain data synchronization across multiple instances. In contrast, Snowflake offers built-in data sharing capabilities, allowing seamless sharing of live data between multiple accounts, departments, or organizations without the need for complex data movement processes.

  5. Concurrency: Oracle traditionally handles concurrency by executing multiple queries concurrently but with some limitations. Snowflake, in contrast, provides robust concurrency management with true parallel execution of queries. Snowflake's architecture ensures that multiple users can run queries concurrently without affecting performance or resource allocation.

  6. Cost Model: Oracle typically employs a fixed cost model, requiring upfront investments in hardware and software licenses. Snowflake, being a cloud-based platform, follows a pay-as-you-go pricing model. This means users are charged only for the resources they consume, allowing for more flexibility and cost optimization.

In Summary, Oracle relies on a traditional on-premises architecture with SQL as its query language, while Snowflake utilizes a cloud-based architecture with a SQL-like language. Snowflake offers better scalability, automatic concurrency management, built-in data sharing capabilities, and a flexible cost model compared to Oracle.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Oracle, Snowflake

Daniel
Daniel

Data Engineer at Dimensigon

Jul 18, 2020

Decided

We have chosen Tibero over Oracle because we want to offer a PL/SQL-as-a-Service that the users can deploy in any Cloud without concerns from our website at some standard cost. With Oracle Database, developers would have to worry about what they implement and the related costs of each feature but the licensing model from Tibero is just 1 price and we have all features included, so we don't have to worry and developers using our SQLaaS neither. PostgreSQL would be open source. We have chosen Tibero over Oracle because we want to offer a PL/SQL that you can deploy in any Cloud without concerns. PostgreSQL would be the open source option but we need to offer an SQLaaS with encryption and more enterprise features in the background and best value option we have found, it was Tibero Database for PL/SQL-based applications.

496k views496k
Comments
Abigail
Abigail

Dec 6, 2019

Decided

In the field of bioinformatics, we regularly work with hierarchical and unstructured document data. Unstructured text data from PDFs, image data from radiographs, phylogenetic trees and cladograms, network graphs, streaming ECG data... none of it fits into a traditional SQL database particularly well. As such, we prefer to use document oriented databases.

MongoDB is probably the oldest component in our stack besides Javascript, having been in it for over 5 years. At the time, we were looking for a technology that could simply cache our data visualization state (stored in JSON) in a database as-is without any destructive normalization. MongoDB was the perfect tool; and has been exceeding expectations ever since.

Trivia fact: some of the earliest electronic medical records (EMRs) used a document oriented database called MUMPS as early as the 1960s, prior to the invention of SQL. MUMPS is still in use today in systems like Epic and VistA, and stores upwards of 40% of all medical records at hospitals. So, we saw MongoDB as something as a 21st century version of the MUMPS database.

540k views540k
Comments
Abigail
Abigail

Dec 10, 2019

Decided

We wanted a JSON datastore that could save the state of our bioinformatics visualizations without destructive normalization. As a leading NoSQL data storage technology, MongoDB has been a perfect fit for our needs. Plus it's open source, and has an enterprise SLA scale-out path, with support of hosted solutions like Atlas. Mongo has been an absolute champ. So much so that SQL and Oracle have begun shipping JSON column types as a new feature for their databases. And when Fast Healthcare Interoperability Resources (FHIR) announced support for JSON, we basically had our FHIR datalake technology.

558k views558k
Comments

Detailed Comparison

Oracle
Oracle
Snowflake
Snowflake

Oracle Database is an RDBMS. An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism is called an object-relational database management system (ORDBMS). Oracle Database has extended the relational model to an object-relational model, making it possible to store complex business models in a relational database.

Snowflake eliminates the administration and management demands of traditional data warehouses and big data platforms. Snowflake is a true data warehouse as a service running on Amazon Web Services (AWS)—no infrastructure to manage and no knobs to turn.

Statistics
Stacks
2.6K
Stacks
1.2K
Followers
1.8K
Followers
1.2K
Votes
113
Votes
27
Pros & Cons
Pros
  • 44
    Reliable
  • 33
    Enterprise
  • 15
    High Availability
  • 5
    Expensive
  • 5
    Hard to maintain
Cons
  • 14
    Expensive
Pros
  • 7
    Public and Private Data Sharing
  • 4
    Good Performance
  • 4
    User Friendly
  • 4
    Multicloud
  • 3
    Great Documentation
Integrations
No integrations available
Python
Python
Apache Spark
Apache Spark
Node.js
Node.js
Looker
Looker
Periscope
Periscope
Mode
Mode

What are some alternatives to Oracle, Snowflake?

MongoDB

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase