Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to create a table in Management Studio and after reading about the new (from SQL 2005 on) NEWSEQUENTIALID() function, thought I'd give it a go.

This is what I'm doing:

enter image description here

But it's not letting me. The error message I get is:

'FormTemplate (Forms)' table - Error validating the default for column 'FormTemplateId'.

Am I missing a trick here? I'm definitely running SQL Server 2008 R2.

share|improve this question
up vote 16 down vote accepted

Use CREATE TABLE, not the GUI.

This is a bug in SSMS, already reported here as well as here on Connect.

share|improve this answer
Thanks. Typical Microsoft attention to detail :-( – 5arx Oct 26 '11 at 10:06
@5arx: poke around the 5 year old critical bugs for MySQL. MS are quite sharp in comparison – gbn Oct 26 '11 at 10:08
@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. It still looks bad to us as customers but as a developer I can understand. – Nick Chammas Oct 26 '11 at 13:11
I'm a developer who uses databases, not a database developer. I haven't seen anyone use raw SQL to create tables since the late 90s. My point is if you're releasing a GUI, make sure it works. That's all. – 5arx Oct 26 '11 at 13:31
The UI doesn't exactly get a lot of priority when it comes to killing bugs. The core engine does, which it should. 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). :( – mrdenny Oct 26 '11 at 16:41

You can work around this bug in SQL Server Management Studio just by ignoring the first and second warning. Changes will be saved.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.