Error validating the default for column id newsequentialid

I would like to have it set by SQL Server Express automatically.There are articles on the web that recommend using one of the following commands as the default value: NEWID() NEWSEQUENTIALID() I put this in VS 2010 column properties of my table, in Default Value or Binding. Are you trying to increment a column ID sequentially upon new insert?A viable workaround is available Thanks again for reporting the product issue and continued support in improving our product.

error validating the default for column id newsequentialid-39error validating the default for column id newsequentialid-74error validating the default for column id newsequentialid-79

Scenarios reported in the bug are not common enough3.On SQL Server, clusters of sequential values can develop when databases (such as contained databases) are moved to other computers. You can use NEWSEQUENTIALID to generate GUIDs to reduce page splits and random IO at the leaf level of indexes.When using Always On and on SQL Database, clusters of sequential values can develop if the database fails over to a different computer. Each GUID generated by using NEWSEQUENTIALID is unique on that studio always gives an error message for tables in which NEWSEQUENTIALID() is used for a default uniqueidentifier column. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server.this is a well known issue since sql2005 but it STILL exists in sql2008!!!!!! NEWSEQUENTIALID() is still a problem in Management Studio (as well as rowversion). Even more of our customers are moving to Postgre SQL each year. MS Senior Management Team , are you sure the cost of discrediting the product is lower than the cost of fixing such an annoying bug? The reasons for closing these bugs are following:1.

Leave a Reply