Javatpoint Logo
Javatpoint Logo



With regards to database management systems (DBMS) like SQL (Structured Query Language), picking the right information types is significant for proficient capacity and recovery of information. Among the usually utilized information types for putting away personal information are Char and VARCHAR. While both fill comparable needs, they have particular contrasts that can influence information base execution and capacity productivity. In this article, we'll dig into the variations among Burn and VARCHAR in SQL.

CHAR Data type

In SQL, the Burn information type is utilized to store fixed-length character strings. At the point when you characterize a section with the Roast information type, you determine the proper length for the information it can hold. This implies that each worth put away in a Scorch segment will possess the specific number of characters determined, no matter what the genuine length of the information.

For example, if you designate a column as CHAR(10), it will always take up 10 characters of storage, even if the actual text stored in the column is less. If the string is less than the specified length, it will be padded with trailing spaces to fill the space.

Here's a quick overview of the CHAR data type:

  • Fixed Length: Scorch segments generally involve the predefined length, cushioning the information with the following spaces is important to meet the characterized length.
  • Appropriate for fixed-length information: Burn is in many cases utilized when you have information that is reliable of similar length, for example, postal codes or fixed-length codes.

CHAR is helpful in situations where you want to guarantee that each worth in a section has a reliable length, yet it might prompt wasteful utilization of extra room while putting away more limited strings.

VARCHAR Data type

In SQL, VARCHAR means "Variable character" and is an information type used to store variable-length character strings. Not at all like Roast, which stores fixed-length strings, VARCHAR sections just use as much extra room depending on the situation to store the real information, without squandering space with the following spaces.

When you define a column with a VARCHAR data type, you specify the maximum length of data it can hold, but the actual storage used depends on the length of the data stored in it e.g., if you define a column as VARCHAR(50). It can store strings up to 50 characters long, but only. The amount of storage necessary for the actual data being stored is used.

  • Variable Length: VARCHAR segments just consume as much extra room depending on the situation for the genuine information put away, with next to no cushioning.
  • Reasonable for variable-length information: VARCHAR is much of the time utilized when you have information with changing lengths, like names, locations, or portrayals.
  • Capacity proficient: VARCHAR can save extra room contrasted with Roast, particularly while putting away more limited strings.

VARCHAR is a flexible information type regularly utilized in SQL data sets for putting away printed information of shifting lengths effectively.


In this schema:

  • EmployeeID and Department are declared as CHAR since they have fixed lengths.
  • FirstName, LastName, Address, and JobTitle are declared as VARCHAR since they can vary in length.

Here's an example of inserting data into this table:

And a query to retrieve employee information:



Following are the Differences between CHAR and VARCHAR

Storage allocation Fixed-length capacity distribution, cushioning strings with spaces to arrive at the characterized length. Variable-length capacity distribution, putting away just the genuine characters without cushioning.
Storage efficiency Less capacity effective, particularly for more limited strings, as it generally utilizes the characterized length. More capacity is effective, especially for more limited strings, as it just proposes the essential measure of capacity.
Padding Naturally cushions strings with spaces to arrive at the predefined length. Doesn't cushion strings; it stores just the real characters given.
Space utilization Can prompt squandered space while putting away more limited strings because of cushioning. Dodges squandered space by powerfully changing capacity in light of the length of the genuine information.
Performance May offer slight execution benefits for fixed-length information because of unsurprising stockpiling size. Can be somewhat slower in specific situations because of variable-length capacity distribution.
Memory usage May consume more memory because of fixed-length capacity. Normally consumes less memory, particularly while putting away more limited strings.
Indexing Ordering Scorch sections can be quicker because of fixed-length capacity. Ordering VARCHAR sections might be somewhat slower because of variable-length capacity.
Suitability Reasonable for fixed-length information, for example, postal codes, country codes, or identifiers. Reasonable for variable-length information like names, locations, or depictions.
Data integrity Guarantees information honesty by authorizing fixed-length imperatives. Adjusts to changing information lengths, permitting greater adaptability yet requiring extra approval assuming explicit length imperatives are essential.
Query optimisation This may prompt more unsurprising questionsabout execution plans because of fixed-length capacity. Inquiry plans might fluctuate depending upon the genuine information length, possibly influencing improvement procedures.

Youtube For Videos Join Our Youtube Channel: Join Now


Help Others, Please Share

facebook twitter pinterest

Learn Latest Tutorials


Trending Technologies

B.Tech / MCA