Microsoft SQL Server vs TiDB

Overview

Microsoft SQL Server

Stacks21.3K

Followers15.5K

Votes540

TiDB

Stacks76

Followers177

Votes28

GitHub Stars39.3K

Forks6.0K

Microsoft SQL Server vs TiDB: What are the differences?

Introduction: Microsoft SQL Server and TiDB are both database management systems, but they have key differences that set them apart in terms of functionality and usage.

Data Storage Architecture: Microsoft SQL Server uses a centralized, master-slave architecture where a single master node controls data transactions and multiple slave nodes replicate the data. In contrast, TiDB is a distributed, cloud-native database that uses a shared-nothing architecture with no single point of control, allowing for horizontal scalability and fault tolerance.
Consistency Model: Microsoft SQL Server follows a strong consistency model, ensuring that all nodes in the database have the most up-to-date data at all times. TiDB, on the other hand, follows a hybrid consistency model that allows users to choose between strong consistency for critical data and eventual consistency for less critical data, providing a balance between data integrity and performance.
Scaling Capabilities: Microsoft SQL Server requires vertical scaling, where additional hardware resources need to be added to a single server to improve performance. In contrast, TiDB can scale horizontally by adding more nodes to the cluster, distributing the workload and increasing capacity without the need for a single powerful server.
Open Source vs. Proprietary: Microsoft SQL Server is a proprietary database management system developed by Microsoft, while TiDB is an open-source distributed database project that can be freely accessed, modified, and distributed under the Apache License. This difference in licensing can impact cost, support, and flexibility for users.
Cloud-Native Features: TiDB is designed as a cloud-native database, with features like automatic sharding, multi-tenancy support, and elasticity to meet the demands of modern cloud-based applications. In contrast, while Microsoft SQL Server can be deployed in the cloud, it may require additional configurations and considerations to fully utilize cloud-native capabilities.
Community Support: TiDB has a growing community of developers and contributors who actively participate in improving the database system, expanding its features, and providing support to users. Microsoft SQL Server, while widely used and supported by Microsoft, may have a more limited community-driven ecosystem for troubleshooting, enhancements, and customizations.

In Summary, Microsoft SQL Server and TiDB differ in their data storage architecture, consistency models, scaling capabilities, licensing, cloud-native features, and community support.

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)

Manual

Advice on Microsoft SQL Server, TiDB

Erin

IT Specialist

Mar 10, 2020

Needs adviceon

Microsoft SQL Server

MySQL

PostgreSQL

I am a Microsoft SQL Server programmer who is a bit out of practice. I have been asked to assist on a new project. The overall purpose is to organize a large number of recordings so that they can be searched. I have an enormous music library but my songs are several hours long. I need to include things like time, date and location of the recording. I don't have a problem with the general database design. I have two primary questions:

I need to use either @{MySQL}|tool:1025| or @{PostgreSQL}|tool:1028| on a @{Linux}|tool:10483| based OS. Which would be better for this application?
I have not dealt with a sound based data type before. How do I store that and put it in a table? Thank you.

668k views668k

Comments

Detailed Comparison

Microsoft SQL Server	TiDB
Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.	Inspired by the design of Google F1, TiDB supports the best features of both traditional RDBMS and NoSQL.
-	Horizontal scalability;Asynchronous schema changes;Consistent distributed transactions;Compatible with MySQL protocol;Written in Go;NewSQL over TiKV;Multiple storage engine support
Statistics
GitHub Stars -	GitHub Stars 39.3K
GitHub Forks -	GitHub Forks 6.0K
Stacks 21.3K	Stacks 76
Followers 15.5K	Followers 177
Votes 540	Votes 28
Pros & Cons
Pros 139 Reliable and easy to use 101 High performance 95 Great with .net 65 Works well with .net 56 Easy to maintain Cons 4 Expensive Licensing 2 Microsoft 1 Allwayon can loose data in asycronious mode 1 Data pages is only 8k 1 Replication can loose the data	Pros 9 Open source 7 Horizontal scalability 5 Strong ACID 3 HTAP 2 Enterprise Support

What are some alternatives to Microsoft SQL Server, TiDB?

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

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 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.

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

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 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

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 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

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.

InfluxDB

InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.

Related Comparisons

Bootstrap vs Materialize

Django vs Laravel vs Node.js

Bootstrap vs Foundation vs Material UI

Node.js vs Spring-Boot

Flyway vs Liquibase

Microsoft SQL Server vs TiDB: What are the differences?

Introduction: Microsoft SQL Server and TiDB are both database management systems, but they have key differences that set them apart in terms of functionality and usage.

Data Storage Architecture: Microsoft SQL Server uses a centralized, master-slave architecture where a single master node controls data transactions and multiple slave nodes replicate the data. In contrast, TiDB is a distributed, cloud-native database that uses a shared-nothing architecture with no single point of control, allowing for horizontal scalability and fault tolerance.
Consistency Model: Microsoft SQL Server follows a strong consistency model, ensuring that all nodes in the database have the most up-to-date data at all times. TiDB, on the other hand, follows a hybrid consistency model that allows users to choose between strong consistency for critical data and eventual consistency for less critical data, providing a balance between data integrity and performance.
Scaling Capabilities: Microsoft SQL Server requires vertical scaling, where additional hardware resources need to be added to a single server to improve performance. In contrast, TiDB can scale horizontally by adding more nodes to the cluster, distributing the workload and increasing capacity without the need for a single powerful server.
Open Source vs. Proprietary: Microsoft SQL Server is a proprietary database management system developed by Microsoft, while TiDB is an open-source distributed database project that can be freely accessed, modified, and distributed under the Apache License. This difference in licensing can impact cost, support, and flexibility for users.
Cloud-Native Features: TiDB is designed as a cloud-native database, with features like automatic sharding, multi-tenancy support, and elasticity to meet the demands of modern cloud-based applications. In contrast, while Microsoft SQL Server can be deployed in the cloud, it may require additional configurations and considerations to fully utilize cloud-native capabilities.
Community Support: TiDB has a growing community of developers and contributors who actively participate in improving the database system, expanding its features, and providing support to users. Microsoft SQL Server, while widely used and supported by Microsoft, may have a more limited community-driven ecosystem for troubleshooting, enhancements, and customizations.

In Summary, Microsoft SQL Server and TiDB differ in their data storage architecture, consistency models, scaling capabilities, licensing, cloud-native features, and community support.