whichdb

ScimoreDB

discontinued

by Scimore UAB · since 2005 · also known as Scimore, ScimoreDB Embedded

Distributed, T-SQL-compatible database for Windows clusters plus an embedded .NET edition; defunct.

relationaldatabase engineproprietarylegacy
Website Compare Find similar

discontinued. No releases or news since late 2013 and the vendor site is gone. For distributed SQL consider CockroachDB, YugabyteDB or Azure SQL; for embedded .NET use SQLite or LiteDB.

Overview

ScimoreDB came from Scimore UAB and offered two things: a shared-nothing distributed SQL database for clusters of commodity Windows servers, and an embedded edition for .NET applications. The distributed version partitioned data across nodes, ran distributed ACID transactions with deadlock detection, executed joins, aggregations, sub-selects and stored procedures in parallel, and aimed for enough SQL Server and T-SQL compatibility to offload large tables from SQL Server; it also had scale-out full-text search and transaction prioritisation. The last news post dates from November 2013 and the scimore.com site had stopped serving the product by 2022, so the product is no longer available.

Transactional apps (OLTP)Embedded / in-processFull-text search

Strengths & trade-offs

Strengths

  • +Scale-out SQL with distributed ACID transactions on cheap Windows hardware
  • +T-SQL compatibility eased offloading tables from SQL Server
  • +Same engine available embedded inside .NET applications
  • +Parallel full-text search across the cluster

Trade-offs

  • −Vendor and product are gone; no support or downloads
  • −Windows-only

Great for

  • +History of distributed SQL on Windows
  • +Migrating legacy ScimoreDB deployments

Think twice for

  • −Any new deployment

Capabilities

Native or official first-party support · 6 of 25 tracked

✓Transactions
✓Joins
✓Secondary indexes
✓Full-text search
✓Stored procedures
✓Durable persistence
–Vector search
–Geospatial
–JSON
–Change data capture
–Triggers
–Materialized views
–TTL / expiry
–Pub/Sub
–Columnar storage
–In-memory
–Compression
–Encryption at rest
–Role-based access
–Time travel
–Branching
–Online schema changes
–Streaming ingest
–Offline sync
–Runs in WebAssembly

Scale & consistency

Comfortable data size
Medium · ≤ 10 TB
Horizontal scaling
Native
Multi-region
No
Transactions
Full ACID
Consistency
Strong
Schema
Strict
Architecture
Distributed, Embedded
Query languages
SQL, T-SQL subset

Shared-nothing partitioning over commodity Windows servers; a customer reported offloading over 5 billion rows from SQL Server.

Deployment

Self-hosted Vendor-managed cloud Serverless Embedded Edge Kubernetes operator

Ecosystem

compatible withSQL Server
used bySPAMfighter

Alternatives to ScimoreDB

Compare all→
CockroachDBRelational47.1

Postgres-wire distributed SQL built to survive node, zone and region failures with serializable transactions.

scimoredb vs cockroachdb →
YugabyteDBRelational32.7

Apache-licensed distributed SQL that reuses the PostgreSQL query layer on a Raft-replicated storage engine.

scimoredb vs yugabytedb →
Azure SQL DatabaseRelational33.9

Microsoft's always-current managed SQL Server engine, from free serverless databases to 128 TB Hyperscale.

scimoredb vs azure-sql-database →
SQLiteRelational75.5

The in-process SQL engine that ships in every phone, browser and OS: one file, zero servers.

scimoredb vs sqlite →
LiteDBDocument10.8

Serverless single-file NoSQL document database for .NET, in the spirit of SQLite.

scimoredb vs litedb →
Microsoft AccessRelational45.8

Desktop database and forms builder bundled with Microsoft 365; still everywhere in back offices.

scimoredb vs microsoft-access →

ScimoreDB FAQ

What is ScimoreDB?

ScimoreDB is a relational database by Scimore UAB, first released in 2005. ScimoreDB came from Scimore UAB and offered two things: a shared-nothing distributed SQL database for clusters of commodity Windows servers, and an embedded edition for .NET applications. The distributed version partitioned data across nodes, ran distributed ACID transactions with deadlock detection, executed joins, aggregations, sub-selects and stored procedures in parallel, and aimed for enough SQL Server and T-SQL compatibility to offload large tables from SQL Server; it also had scale-out full-text search and transaction prioritisation. The last news post dates from November 2013 and the scimore.com site had stopped serving the product by 2022, so the product is no longer available.

Is ScimoreDB open source?

No. ScimoreDB is proprietary, closed-source software.

Does ScimoreDB support ACID transactions?

Yes. ScimoreDB supports full ACID transactions, with strong consistency.

Does ScimoreDB scale horizontally?

ScimoreDB scales horizontally out of the box, with built-in sharding or partitioning. It is comfortable at medium scale (≤ 10 TB).

How can I run ScimoreDB?

You can self-host it and embed it in your application.

What is ScimoreDB best for?

ScimoreDB is a strong fit for history of distributed SQL on Windows and migrating legacy ScimoreDB deployments. Think twice for any new deployment.

What are the best alternatives to ScimoreDB?

Common alternatives to ScimoreDB include CockroachDB, YugabyteDB, Azure SQL Database, SQLite and LiteDB. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.

Is ScimoreDB still maintained?

ScimoreDB is discontinued. No releases or news since late 2013 and the vendor site is gone. For distributed SQL consider CockroachDB, YugabyteDB or Azure SQL; for embedded .NET use SQLite or LiteDB.

How popular is ScimoreDB?

ScimoreDB has little measurable public adoption today, so it ranks near the bottom of the WhichDB Score.