SQL_Enthusiast (2/20/2013)

---

it can't just be random because it's supposed to be unique, correct?)

SQL_Enthusiast (2/20/2013)

---

2. How does a NEWID() get ordered by?

ORDER BY NEWID() ASC 

[b]a. Does it look at the most left character(s) and say, "You start with an "H...", you with a "BD...", you with a "BA..." you with a "9...", and you with a "3..."; therefore, return you in this order BA..., BD..., H..., 3..., 9...")

why you think that random cant be unique ? sql server internally generate this 32 bit alphanumeric code.

SQL_Enthusiast (2/21/2013)

---

Bhuvnesh,
Thank you for the response.



I didn't mean random like, "What is my eight year boy going to do next?" That is truly random. I meant, there has to be a rhyme or reason (aka logic) behind how to "randomly" generates the 32 bit alphanumeric code. Does anyone know the logic on how it builds that character string? Does it use the MAC address, date, time, tap into my deepest thoughts and encrypt them

ramesh.sadhu21 (2/22/2013)

---

If you covert this New ID as integer then you can easily identify uniqueness and if you order by this then you will get the result in manner

Lynn Pettis (2/22/2013)

---

I haven't tried, but are you sure you can convert a uniqueidentifier to a bigint?

SELECT CAST(CAST(NEWID() AS BINARY(16)) AS BIGINT)

Jeff Moden (2/22/2013)

---

Yes, but not directly.

SELECT CAST(CAST(NEWID() AS BINARY(16)) AS BIGINT)

Lynn Pettis (2/22/2013)

---

As to ordering by a uniqueidentifier, it sorts in ascending or descending order as if it is converted to a CHAR(36) value, or at least that is my experience with them.

DECLARE @T AS TABLE (uuid uniqueidentifier);

INSERT @T
    (uuid)
VALUES 
    ({ guid'459F82E6-4C50-4777-8347-D313526EB4BA'}),
    ({ guid'E99F760A-80EC-40A7-B7E9-88F58006AA13'});

SELECT uuid FROM @T AS t ORDER BY t.uuid;