In SQL, TINYINT is a data type used to store integer values, typically representing small whole numbers. It is a compact data type that takes up very little storage space compared to larger integer types like INT or BIGINT. The TINYINT data type is primarily used when you need to conserve storage space or when you know that the values to be stored will always be within a small range.

Key characteristics

Here are some key characteristics of the TINYINT data type:

Storage Size: The TINYINT data type typically occupies 1 byte of storage. This allows it to store values in the range of -128 to 127 for signed TINYINT and 0 to 255 for unsigned TINYINT. The signed version can store both positive and negative values, while the unsigned version can only store positive values.

Range: The range of values that can be stored in a TINYINT column is limited compared to larger integer data types like INT or BIGINT. However, it is often sufficient for scenarios where you only need to store small numbers, such as representing binary flags, status codes, or small counters.

Performance: Because of its small storage size, TINYINT columns can be more efficient in terms of storage and processing performance when compared to larger integer data types. This can be especially important in large-scale databases where storage efficiency and query performance are critical.

Compatibility: The TINYINT is a commonly supported data type across various relational database management systems (RDBMS), including MySQL, PostgreSQL, SQL Server, and others. This means that you can use it consistently across different database platforms.


Here’s an example of creating a TINYINT column in a SQL table:

    FirstName VARCHAR(50),
    LastName VARCHAR(50),

In this example, the “Age” column is defined as a TINYINT, indicating that it will store small integer values representing the age of employees. It is important to note that the specific range and behavior of TINYINT may vary slightly depending on the database system you are using, so it’s essential to consult the documentation of your chosen RDBMS for detailed information.