Error validating the default for column rowguid
It has many downsides which newid() does not, and none of the benefits - the biggest being that newid() is not practically predictable, whereas newsequentialid() is.If you are not worried about fragmentation, what's the point?Otherwise, it seems to behave similarly to newid() / Row Guid.
I created a column in a table with datatype uniqueidentifier which is set as Row GUID and the default value to newsequentialid().
So if you run the inserts at different time you'll see some gaps.
But the important part is that the Guid are "ordered" in a way that do not cause page splits (if the Guid is used in a index) and this is what happens when using the new sequential guid.
Replication supports a wide range of schema changes to published objects.
When you make any of the following schema changes on the appropriate published object at a Microsoft SQL Server Publisher, that change is propagated by default to all SQL Server Subscribers: Important Schema changes to tables must be made by using Transact-SQL or SQL Server Management Objects (SMO).