GUID or Varchar(36)?

Skip to main content

Command Palette

Search for a command to run...

GUID or Varchar(36)?

PublishedAugust 27, 2015

•2 min read•View as Markdown

GUID or Varchar(36)?

Emmanuel Tissera

Technical Director at Luminary. Umbraco 3x MVP.

On this page

First off, what is a GUID?Why compare against Varchar(36)?So what performs better?Caveats

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Tiny Elf - Transferring ownership of automated triggers

Instructions

Oct 9, 2025·2 min read·15

Tiny Elf - Transferring ownership of automated triggers

I dug a trench and unearthed some Software Engineering principles

How does this even compute? What has digging a trench have to do with Software Engineering and building products?

Aug 3, 2023·8 min read·241

I dug a trench and unearthed some Software Engineering principles

Happy Birthday, Luminary - H5YR!

My workplace Luminary turned 24 on 1-July-2023.

Jul 1, 2023·4 min read·333

Happy Birthday, Luminary - H5YR!

Content delivery API in Umbraco 12 RC 1 - Did I say Headless?

Headless in Umbraco core

May 18, 2023·6 min read·504

Content delivery API in Umbraco 12 RC 1 - Did I say Headless?

Tiny Elf - a Slack bot with Google sheets and Typescript

Automate meeting host rotations within your team with some smarts

Oct 30, 2022·8 min read·254

Tiny Elf - a Slack bot with Google sheets and Typescript

A

An EmmTi Blog

76 posts

Some random and not-so-random stuff I came across today and couldn't help keep silent about!

While working on an application which had a foreign key GUID reference, we had to change the implementation for that field to accept a string. Then we came across the question as to whether GUIDs or a Varchar(36) field would perform better?

First off, what is a GUID?

In essence a GUID is an integer value. Of course, it is a 128 bit integer value taking 16 bytes to store. What we usually see (b6aa92e9-5ae9-47f4-ad2f-ebc36452c61d) is the human readable hexadecimal string. But GUID values are not stored or processed as strings. The other difference to a 128-bit integer is how the next GUID is generated – randomly, rather than sequentially.

See comments in this article for more info:
http://blog.sqlauthority.com/2010/04/28/sql-server-guid-vs-int-your-opinion/

Why compare against Varchar(36)?

That's because the hexadecimal representation of a GUID is 36 characters long. So if you are storing the GUID as a string, you need a Varchar(36) field.

See this article on the pros and cons:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/df3caee5-3751-469b-a943-f0c8cb501f75/unique-identifier-vs-varchar36-for-storing-guids?forum=transactsql

So what performs better?

Having said that a GUID takes 16 bytes and Varchar(36) takes 36 bytes, the GUID will always outperform it's counterpart. Other than that, it would be somewhat faster to compare GUID values because it's a simple numeric comparison and doesn't have to consider lexical rules.

Caveats

If it is either a GUID or Varchar(36) field, make sure that it is indexed to have a performance gain. Also consider your requirements to make sure what suits you best.

This article was originally written on Google's Blogger platform and ported to Hashnode on 17 Sep 2022.

#sql #guid #varchar

1.6K views

© 2026 An EmmTi Blog

Members
Archive
Privacy
Terms