Hi Dave,
The constraint was removed since it is no longer being used - so basically if it was not there, it is OK, just, you may need to run this part of the query which was probably not executed after the error:
ALTER TABLE [CMS_WebPartLayout]
DROP
COLUMN [WebPartLayoutCheckedOutByUserID],
COLUMN [WebPartLayoutCheckedOutFilename],
COLUMN [WebPartLayoutCheckedOutMachineName];
ALTER TABLE [CMS_WebPartLayout]
ADD
CONSTRAINT [DEFAULT_CMS_WebPartLayout_WebPartLayoutCodeName]
DEFAULT ('') FOR [WebPartLayoutCodeName],
CONSTRAINT [DEFAULT_CMS_WebPartLayout_WebPartLayoutDisplayName]
DEFAULT ('') FOR [WebPartLayoutDisplayName];
In general, if you have big DB with many records, it is better to run the SQL script directly over the DB using SQL management studio to avoid time outs.
Best regards,
Juraj Ondrus