@5arx Well, when you consider the number of products Microsoft supports and the new features they add with every release, I think it's understandable that an easily avoidable bug in the GUI should linger for years.

looking for a nice man website for dating - Sql server newsequentialid error validating the default for column

My point is if you're releasing a GUI, make sure it works. The UI doesn't exactly get a lot of priority when it comes to killing bugs. The UI team doesn't exactly have a whole lot of guys on it so they get to what they can as dictated by management (if it isn't Azure at the moment it isn't getting fixed).

The text of the Default Value property is inconsistent with one or more of the column's settings.

Select the box to the left of the column name that you want to reorder.

Drag the column to another location within the table.

I moved Then I clicked the "Generate Change Script" button, and here is the monstrosity that it created (and note this is a heap with no keys, constraints, triggers etc. /* To prevent any potential data loss issues, you should review this script in detail before running it outside the context of the database designer.

*/ BEGIN TRANSACTION SET QUOTED_IDENTIFIER ON SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET CONCAT_NULL_YIELDS_NULL ON SET ANSI_NULLS ON SET ANSI_PADDING ON SET ANSI_WARNINGS ON COMMIT BEGIN TRANSACTION GO CREATE TABLE dbo.Note that there is no discernible pattern when using NEWID().GUIDs have a staggering amount of potential values (2^122) - making Big Int look like a speck in comparison), although storage and performance would prevent that number from ever being reached in the real world.This is because the NEWID() function causes random activity and uses fewer cached data pages.Using the NEWSEQUENTIALID() function also helps to completely fill the index and data pages.The most common reason for this is that the default value does not conform to the column's data type.