Created FK using sql but "CREATE SCRIPT" not same

Question

I used this to create a FK relationship between  a Parent and Child table.
     ALTER TABLE [dbo].[Child]
     ADD  CONSTRAINT [FK_Child_Parent]
     FOREIGN KEY([Pid])
     REFERENCES [dbo].[Parent] ([pid])
     GO
When I scripted the relationship (under SSMS) this was returned....
     ALTER TABLE [dbo].[Child]  WITH CHECK ADD  CONSTRAINT [FK_Child_Parent] FOREIGN KEY([Pid])
     REFERENCES [dbo].[Parent] ([pid])
     GO
      ALTER TABLE [dbo].[Child] CHECK CONSTRAINT [FK_Child_Parent]
      GO
Note the addition of "CHECK CONSTRAINT" and now there are two statements What does that do that my original statement didn't?
TIA,
edm2

Answer 1

It does nothing different.  This is just another instance of SSMS explicitly scripting out the current state of the object, and explicitly specifying every possible option, even if the current value is the same as the default setting.
The first statement creates the constraint, checks the existing data and enables the constraint.  The second statement enables the constraint.
The reason it uses two statements is probably because you cannot create a CHECK CONSTRAINT and disable it in a single statement.  If you want to, you must use two statements.  So SSMS appears to be coded to always use two statements: one to create
the constraint and one to set it's enabled/disabled state.  IE because it sometimes requires two statements to create a CHECK CONSTRAINT in the desired state, SSMS always uses two statements, because it's simpler to code the script generator that way.
David
David http://blogs.msdn.com/b/dbrowne/