DBMS > Infobright vs. Microsoft Access vs. Snowflake vs. Splice Machine

System Properties Comparison Infobright vs. Microsoft Access vs. Snowflake vs. Splice Machine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Cloud-based data warehousing service for structured and semi-structured data

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.54
Rank	#255	Overall
	#116	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

www.microsoft.com/en-us/microsoft-365/access

www.snowflake.com

splicemachine.com

Technical documentation

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

splicemachine.com/how-it-works

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

Snowflake Computing Inc.

Splice Machine

Initial release

2005

1992

2014

Current release

1902 (16.0.11328.20222), March 2019

3.1, March 2021

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Bundled with Microsoft Office

commercial

Open Source

AGPL 3.0, commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

Linux
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

JavaScript (Node.js)
Python

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

yes

Java

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

a simple user-level security was built in till version Access 2003

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users, groups and roles according to SQL-standard

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.