{"id":28,"date":"2011-06-30T11:17:47","date_gmt":"2011-06-30T11:17:47","guid":{"rendered":"https:\/\/sqlserverlearner.azurewebsites.net\/2011\/06\/30\/what-is-newsequentialid\/"},"modified":"2011-06-30T11:17:47","modified_gmt":"2011-06-30T11:17:47","slug":"what-is-newsequentialid","status":"publish","type":"post","link":"https:\/\/sqlserverlearner.com\/2011\/06\/30\/what-is-newsequentialid\/","title":{"rendered":"What is NEWSEQUENTIALID()"},"content":{"rendered":"<p><strong>NEWSEQUENTIALID()<\/strong><\/p>\n<p>New NEWSEQUENTIALID generates new GUID.<\/p>\n<p>The GUID generated is always greater than GUID that was previously generated.<\/p>\n<p>Thus the new values inserted into tables using NEWSEQUENTIALID are in assending order and helps to fill index pages easyly.<\/p>\n<p>NEWSEQUENTIALID is faster in operation than NEWID.<\/p>\n<p><strong>If a GUID Column in a table has to be bound with a unique Identifier then using NEWSEQUENTIALID is preferred.But the values can be predicted<\/strong><\/p>\n<p>NEWSEQUENTIALID cannot be used in queries like NEWID.<\/p>\n<p>[sql] SELECT NEWSEQUENTIALID() [\/sql]<\/p>\n<p>The above query would raise an error:<\/p>\n<p><font color=\"red\">The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type &#8216;uniqueidentifier&#8217; in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression.<\/font><\/p>\n<p>Syntax for using NEWSEQUENTIALID with tables:<br \/>\n[sql]CREATE TABLE Table1 (Col1 uniqueidentifier DEFAULT NEWSEQUENTIALID()) [\/sql]<\/p>\n<p><strong>How are values inserted into columns with NEWSEQUENTIALID?<\/strong><\/p>\n<p>[sql]CREATE TABLE Table1 (Col1 uniqueidentifier DEFAULT NEWSEQUENTIALID())<br \/>\nGO<\/p>\n<p>INSERT INTO Table1(Col1)<br \/>\nVALUES (DEFAULT)<\/p>\n<p>INSERT INTO Table1(Col1)<br \/>\nVALUES (DEFAULT)<\/p>\n<p>INSERT INTO Table1(Col1)<br \/>\nVALUES (DEFAULT)<\/p>\n<p>INSERT INTO Table1(Col1)<br \/>\nVALUES (DEFAULT)<br \/>\nGO<\/p>\n<p>SELECT * FROM TABLE1<br \/>\nGO[\/sql]<\/p>\n<p>The output of the above query will be something like this:<br \/>\n07D7AE4D-97A3-E011-B424-0021971FCF00<br \/>\n08D7AE4D-97A3-E011-B424-0021971FCF00<br \/>\n09D7AE4D-97A3-E011-B424-0021971FCF00<br \/>\n0AD7AE4D-97A3-E011-B424-0021971FCF00<\/p>\n<p>It can be seen that the values here are in sequence.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>NEWSEQUENTIALID() New NEWSEQUENTIALID generates new GUID. The GUID generated is always greater than GUID that was previously generated. Thus the new values inserted into tables using NEWSEQUENTIALID are in assending order and helps to fill index pages easyly. NEWSEQUENTIALID is faster in operation than NEWID. If a GUID Column in a table has to be&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[41],"tags":[89,90,91,92],"_links":{"self":[{"href":"https:\/\/sqlserverlearner.com\/wp-json\/wp\/v2\/posts\/28"}],"collection":[{"href":"https:\/\/sqlserverlearner.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sqlserverlearner.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sqlserverlearner.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sqlserverlearner.com\/wp-json\/wp\/v2\/comments?post=28"}],"version-history":[{"count":0,"href":"https:\/\/sqlserverlearner.com\/wp-json\/wp\/v2\/posts\/28\/revisions"}],"wp:attachment":[{"href":"https:\/\/sqlserverlearner.com\/wp-json\/wp\/v2\/media?parent=28"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sqlserverlearner.com\/wp-json\/wp\/v2\/categories?post=28"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sqlserverlearner.com\/wp-json\/wp\/v2\/tags?post=28"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}