Hello,

I am creating a new database and I was advised to use Sequential Guids.
I was reading some information and, as far as I understood, I can use NEWSEQUENTIALID. This can be used when I have a uniqueidentifier column as the key of a clustered index to avoid fragmentation during insert.

Ok, so I use NEWSEQUENTIALID instead of NEWID.

But I will use LINQ most of the time instead of Stored Procedures.

So can I specify in my tables scripts to use Sequential Guids when, for example, a record is created?
 
And am I right when using Sequential Guids?

Here is a part of my code:

-- Blogs  ...
create table dbo.Blogs
(
    BlogID uniqueidentifier not null
        constraint PK_Blog primary key clustered,
    Title nvarchar(400) null,
    Description nvarchar(2000) null,
    CreatedDate datetime null
)

-- Posts ...
create table dbo.Posts
(
    PostID uniqueidentifier not null
      constraint PK_Post primary key clustered,
    BlogID uniqueidentifier not null,
    AuthorID uniqueidentifier not null,
    Title nchar(1000) null,
    Body nvarchar(max) null,
    UpdatedDate datetime not null,
    IsPublished bit not null,
        constraint FK_Posts_Blogs
            foreign key(BlogID)
            references dbo.Blogs(BlogID)    
            on delete cascade,            
        constraint FK_Posts_Users
            foreign key(AuthorID)
            references dbo.Users(UserID)    
            on delete cascade     

 Hi Miguel,

                 You are able to use the DEFAULT option set to NEWSEQUENTIALID() function for the BlogID and PostID column. I've read that on SqlServer Books on line.

                   I hope it helps.

Regards,

Fernando
 

By Default, the property "Auto Generated Value" is not set, changing this fixes your problem.

 More info can be found here.