DBMS > Interbase vs. Microsoft SQL Server vs. Percona Server for MySQL vs. PouchDB vs. Splunk

System Properties Comparison Interbase vs. Microsoft SQL Server vs. Percona Server for MySQL vs. PouchDB vs. Splunk

Editorial information provided by DB-Engines

Name

Description

Light-weight proven RDBMS

originally from Borland

Microsofts flagship relational DBMS

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

JavaScript DBMS with an API inspired by CouchDB

Analytics Platform for Big Data

Primary database model

Relational DBMS

Document store

Search engine

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.embarcadero.com/products/interbase

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

www.percona.com/software/mysql-database/percona-server

pouchdb.com

www.splunk.com

Technical documentation

docs.embarcadero.com/products/interbase

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

www.percona.com/downloads/Percona-Server-LATEST

pouchdb.com/guides

docs.splunk.com/Documentation/Splunk

Developer

Embarcadero

Microsoft

Percona

Apache Software Foundation

Splunk Inc.

Initial release

1984

1989

2008

2012

2003

Current release

InterBase 2020, December 2019

SQL Server 2022, November 2022

8.0.36-28, 2024

7.1.1, June 2019

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL version 2

Open Source

commercial

Limited free edition and free developer edition available

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.

Implementation language

C++

C and C++

JavaScript

Server operating systems

Android
iOS
Linux
OS X
Windows

Linux
Windows

Linux

server-less, requires a JavaScript environment (browser, Node.js)

Linux
OS X
Solaris
Windows

Data scheme

yes

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.

export as XML data possible

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
ODBC

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

ADO.NET
JDBC
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

HTTP REST

Supported programming languages

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

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

JavaScript

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

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

yes

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication
XtraDB Cluster

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

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.