title: Is there a reason to specify DEFAULT (NULL) on a nullable column?
body: <p>I have a table created like this originally:</p>
  
  <pre><code>CREATE TABLE dbo.XX (
  YY int DEFAULT(NULL)
  )
  </code></pre>
  
  <p>If you do this, and then script the table later on, you will get the following code, plus a randomly named default constraint:</p>
  
  <pre><code>CREATE TABLE [dbo].XX([YY] [int] NULL) 
  GO
  ALTER TABLE [dbo].XX ADD  DEFAULT (NULL) FOR [YY]
  GO
  </code></pre>
  
  <p>Now is there any real point in specifying <code>DEFAULT (NULL)</code> on a column instead of just leaving it as <code>[YY] [int] NULL</code> in the first place?</p>