DBMS > Apache Drill vs. Graph Engine vs. Microsoft SQL Server vs. TimesTen

System Properties Comparison Apache Drill vs. Graph Engine vs. Microsoft SQL Server vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Microsofts flagship relational DBMS

In-Memory RDBMS compatible to Oracle

Primary database model

Document store
Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

drill.apache.org

www.graphengine.io

www.microsoft.com/en-us/sql-server

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

drill.apache.org/docs

www.graphengine.io/docs/manual

learn.microsoft.com/en-US/sql/sql-server

docs.oracle.com/database/timesten-18.1

Developer

Apache Software Foundation

Microsoft

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

2010

1989

1998

Current release

1.20.3, January 2023

SQL Server 2022, November 2022

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

MIT License

commercial

restricted free version is available

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

.NET and C

C++

Server operating systems

Linux
OS X
Windows

.NET

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

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

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C++

C#
C++
F#
Visual Basic

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

by means of logfiles and checkpoints

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights 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.