Re: Document atthasmissing default optimization avoids verification table scan

Or, we can leave it where things are and make sure the reader understands there are two paths to having a NOT NULL constraint on the newly added column.  Something like:

"If you plan on having a NOT NULL constraint on the newly added column you should add it as a column constraint during the ADD COLUMN command.  If you add it later via ALTER COLUMN SET NOT NULL the table will have to be completely scanned in order to ensure that no null values were inserted."

David J.