views:

28

answers:

3

In SQL Server, I have a new column on a table:

ALTER TABLE t_tableName 
    ADD newColumn NOT NULL

This fails because I specify NOT NULL without specifying a default constraint. The table should not have a default constraint.

To get around this, I could create the table with the default constraint and then remove it.

However, there doesn't appear to be any way to specify that the default constraint should be named as part of this statement, so my only way to get rid of it is to have a stored procedure which looks it up in the sys.default_constraints table.

This is a bit messy/verbose for an operation which is likely to happen a lot. Does anyone have any better solutions for this?

A: 

I could create the column without the NOT NULL, run an update on the existing date, then alter the column to have the NOT NULL. I am concerned about the performance implications of this, for example if it were on a multi-million row table, so this seems less than ideal.

GlennS
+3  A: 

This should work:

ALTER TABLE t_tableName 
    ADD newColumn VARCHAR(50)
    CONSTRAINT YourContraintName DEFAULT '' NOT NULL
Joe Stefanelli
@Mitch: I just tested this on both 2005 and 2008 to make sure and it works as written.
Joe Stefanelli
@Joe: aplogies. I didn't know that syntax worked.
Mitch Wheat
+2  A: 
ALTER TABLE t_tableName 
    ADD newColumn int NOT NULL
        CONSTRAINT DF_defaultvalue DEFAULT (1)
Mitch Wheat