What is data?
Data are raw facts, symbols, or observations—numbers, text, dates, images, clicks—that have meaning when interpreted in context. Information is data that has been processed into a useful form for decisions or actions.
Master database management systems with notes, queries, interviews, and cheatsheets—covering SQL engines and NoSQL patterns in one place.
Data are raw facts, symbols, or observations—numbers, text, dates, images, clicks—that have meaning when interpreted in context. Information is data that has been processed into a useful form for decisions or actions.
A database is an organized collection of related data stored so it can be searched, updated, and shared efficiently. It is usually managed by software (a DBMS) rather than only loose files.
A Database Management System (DBMS) is software that creates, maintains, and controls access to a database. It provides storage, querying, security, backup, concurrency control, and often a query language (commonly SQL for relational systems).
| Aspect | DBMS | RDBMS | ORDBMS |
|---|---|---|---|
| Meaning | General term: software to define, store, and access data. | Relational DBMS: data in tables with rows/columns, relationships via keys. | Object-relational: relational model extended with object features (e.g. user-defined types, methods). |
| Data model | Can be hierarchical, network, file-oriented, or relational. | Tables, primary/foreign keys, normalization, SQL. | Tables + objects (inheritance, complex types) mapped to relational storage. |
| Typical examples | Early IMS-style systems; “DBMS” often used loosely for any database engine. | MySQL, Oracle Database, Microsoft SQL Server, PostgreSQL. | PostgreSQL (with extensions), Oracle (object features). |
| Topic | SQL (relational) | NoSQL |
|---|---|---|
| Structure | Tables, fixed schema (with migrations for changes). | Document, key-value, wide-column, or graph—often flexible or schemaless. |
| Query | Declarative SQL (JOINs, aggregations). | APIs or specialized query languages (e.g. MQL for MongoDB). |
| Scaling pattern | Vertical scaling, replication; sharding is possible but more involved. | Often designed for horizontal scaling and partition tolerance. |
| Good for | ACID transactions, complex reporting, strong consistency needs. | Rapid iteration, variable shapes (e.g. JSON), very large distributed writes. |
| Examples | MySQL, Oracle, SQL Server. | MongoDB, Cassandra, Redis, Neo4j. |
| Aspect | MySQL | Oracle | SQL Server | MongoDB |
|---|---|---|---|---|
| Category | Relational (RDBMS) | Relational (RDBMS) | Relational (RDBMS) | Document-oriented NoSQL |
| Typical use | Web apps, LAMP/LEMP stacks, SaaS backends. | Enterprise OLTP, large deployments, packaged apps. | Microsoft ecosystem, .NET, BI integration. | JSON-like documents, flexible schemas, agile product data. |
| Primary interface | SQL | SQL + PL/SQL | SQL + T-SQL | MQL / drivers (often used from app code) |
| Licensing / editions | Open source (GPL) and commercial (e.g. Oracle MySQL offerings). | Commercial focus; free tiers for learning (check current Oracle terms). | Commercial; Developer/Express editions for learning/dev. | Server Side Public License (SSPL) community edition; commercial Atlas/enterprise. |
| Transactions | ACID with InnoDB (default). | Strong ACID, advanced isolation options. | ACID, tight Windows/Azure integration. | Multi-document ACID since v4.0+; replica sets for durability. |
| Notable strength | Simple ops, wide hosting support, huge community. | Maturity, advanced features, RAC/high availability options. | SSIS/SSRS/SSAS, T-SQL, Azure SQL. | Nested documents, horizontal scaling, aggregation pipelines. |
Use the Database Systems cards below for notes, queries, interviews, certifications, and cheatsheets.