PM & AI Chronicles

From Product Thinking to Prompt Engineering – One Tool at a Time

Database Data Types 🔤: The Building Blocks of Data in SQL & NoSQL 🧱🧊

A Look Inside Database Data Types: How Information Becomes Values in SQL & NoSQL ℹ️📄

This article is part of the Database Fundamentals Series — where we break down what databases are, how they store information, and how data is organized, accessed, and used behind the scenes. 👉 — Database Fundamentals: Foundation of Data Storage

Every piece of information stored in a database — whether it’s a person’s name, an order amount, a date of birth, or even a full JSON document — has a type.
This “type” tells the database what kind of data it is, how much space it needs, and what operations you can perform on it. Think of data types as the labels on containers in a kitchen:

  • Flour goes in a jar.
  • Milk goes in a bottle.
  • Vegetables go in the fridge.

If you mix them up or put something in the wrong container, things stop working. Databases work the same way.

Are Data Types Different in RDBMS and NoSQL? ⭐ 🌃

Yes — but also no. Both relational (SQL) and non-relational (NoSQL) databases use data types, but they don’t follow the same rules.

Relational databases (SQL) are strict.

  • Every column must have a defined data type.
  • The structure is fixed.
  • Types are enforced strongly.

NoSQL databases are flexible.

  • They don’t always require a predefined type.
  • A field in one document can hold a number, while the same field in another document might hold text.
  • Some NoSQL systems infer types automatically.
  • This difference comes from their design philosophies:
  • SQL databases want consistency, structure, and accuracy.
  • NoSQL databases want flexibility, agility, and scale.

Are There Common Data Types Used in Both? ✅

Even though SQL and NoSQL store data differently, some basic types — like numbers, text, dates, and Boolean values — are used everywhere. How these types are named or enforced may vary, but the concept is the same.

The Main Families of Database Data Types 🧱 ⛓️

Don’t worry — this is the “no heavy tech jargon, no headache” version of data types. If you can tell the difference between a number and your name, you’re already qualified to read this article. 😄

Databases support many data types, but almost all of them fall into a few simple categories. Below is a beginner-friendly explanation of each category, how they’re used, and whether they appear in SQL, NoSQL, or both.

Numeric Data Types 🔢

Used when you want to store numbers — either whole numbers or numbers with decimals.

✔️ Used In: SQL & NoSQL

Whole Numbers (Integers)

  • INT, SMALLINT, BIGINT
  • Store counts or identifiers.
  • Example: number of items ordered → 3

Decimal & Money Values (Exact Numbers)

  • DECIMAL(p,s)
  • Great for prices or financial data where accuracy matters.
  • Example: product price → 19.99

Approximate Numbers

  • FLOAT, REAL
  • Used for scientific calculations or values that don’t need perfect precision.
  • Example: temperature reading → 98.6

📝 In NoSQL: you just store them as “number,” but internally it still handles integers vs decimals.

Character / String Data Types 🔠

Used for text — names, product descriptions, emails, anything made of letters or symbols.

✔️ Used In: SQL & NoSQL

Fixed-Length Text

  • CHAR(n)
  • Used when the text is always the same length.
  • Example: country code → “USA”

Variable-Length Text

  • VARCHAR(n)
  • Most common for text that varies in size.
  • Example: person’s name → “William John”

Large Text Blocks

  • TEXT, NTEXT
  • Good for long notes, descriptions, or documents.
  • Example: blog content → “This article explains…”

📝 In NoSQL: stored as strings or large text values in JSON documents.

Date & Time Data Types 📆🕧

Used to store when something happened — dates, times, or both.

✔️ Used In: SQL & NoSQL

Date Only

  • DATE → 2025-07-25
  • Used for birthdays or event dates.

Time Only

  • TIME → 13:45:00
  • Used for capturing reservation times or logs.

Date + Time

  • DATETIME, DATETIME2 → 2025-07-25 13:45:00

Timestamp / Last Updated

  • TIMESTAMP
  • Mostly used to track when a record was created or modified.

Time Zone–Aware

  • DATETIMEOFFSET
  • Stores date/time along with the timezone.

📝 In NoSQL: stored as strings or numbers, depending on the database (for example, MongoDB has a native Date type).

Boolean Data Types ❌✅

Used for simple true/false logic.

✔️ Used In: SQL & NoSQL

  • BOOLEAN or BIT
  • Example:
    • isActive = TRUE
    • emailVerified = FALSE

This is one of the simplest and most universal data types.

Binary & File Data Types 0️⃣1️⃣

Used for storing non-text data such as images, audio, PDFs, or encrypted values.

✔️ Used In: SQL & NoSQL

Raw Binary Data

  • BINARY, VARBINARY
  • Used for things like encrypted passwords.

Large Binary Objects

  • BLOB
  • Example: a profile picture stored inside a record.

📝 In NoSQL: Often stored as Base64 strings or binary buffers.

Special Data Types ✨

These types are not needed everywhere, but are extremely useful in certain applications.

✔️ Used In:

  • SQL → most of these
  • NoSQL → JSON is native; others vary depending on the database

JSON

  • Stores structured data inside one field.
  • Extremely popular in NoSQL and supported in most modern SQL engines.

Example:

{"name": "Alex", "age": 30}

XML

  • Older format used for nested, structured data.
  • Still supported in enterprise SQL systems.

GUID / Unique Identifier

  • UNIQUEIDENTIFIER
  • Used to generate globally unique IDs across systems.
  • Example: 550e8400-e29b-41d4-a716-446655440000

Spatial Data Types

  • GEOMETRY, GEOGRAPHY
  • Used by mapping, GPS, and location-based apps.
  • Example: storing coordinates for a store location.

📝 In NoSQL:

  • JSON is the most widely used.
  • Spatial/geolocation types vary by platform (e.g., MongoDB has native GeoJSON support).

SQL vs. NoSQL Data Types — Quick Comparison Table 📊

Data Type CategorySQL (Relational)NoSQL (Non-Relational)Beginner Explanation
NumbersINT, BIGINT, DECIMAL, FLOATJust “Number” (flexible)SQL is strict, NoSQL is chill.
TextCHAR, VARCHAR, TEXTString, long textUsed for names, messages, descriptions.
Date & TimeDATE, TIME, DATETIME, TIMESTAMPStored as date objects or stringsSQL has many flavors, NoSQL keeps it simple.
BooleanTRUE/FALSE or BITTRUE/FALSESame idea everywhere.
Binary (Files)BINARY, VARBINARY, BLOBBinary or Base64Used for images, audio, documents.
JSON / XMLJSON, XML (supported in modern SQL)Native JSON (common)For storing nested, structured data.
Spatial (Maps/GPS)GEOGRAPHY, GEOMETRYGeoJSON (varies by system)Used for coordinates and map data.
GUID / Unique IDUNIQUEIDENTIFIERObjectId or random IDsFor generating globally unique IDs.

Wrapping Up 🧭

Data types may sound technical at first, but now you’ve seen that they’re really just different containers for different kinds of information. Whether you’re using a strict SQL database or a flexible NoSQL one, the idea stays the same:

  • Numbers stay numbers
  • Text stays text
  • Dates track time
  • Booleans answer yes/no
  • And special types help you store unique things like JSON, maps, or even images

Think of data types as the database’s way of keeping your information organized, predictable, and usable — without making you solve a math puzzle every time you add a new record. As you keep exploring databases, you’ll notice that these building blocks will appear everywhere.

And now, you know exactly what they mean and when to use them. 👋 On that note, you’re now officially “data-type literate.”