Column marked NOT NULL. No default value. Update may fail.

Compares and synchronizes SQL Server databases, backups and scripts.

Moderators: JonathanWatts, Chris Auckland, David Atkinson, eddie davis, Anu Deshpande, Michelle Taylor, alice.easey, james.billings, chengvoon.tong

Column marked NOT NULL. No default value. Update may fail.

Postby duanecwilson » Wed Sep 26, 2012 3:47 pm

I am getting the following error when deploying with SQL Compare:

The column on table is being marked as NOT NULL. There is no default value so the update may fail.

Most of these columns are part of a compound key so I cannot set them as nullable. I am wondering if I should create a default of an empty string or zero length string, and if it is numeric, what to use.

Or is this error ignorable as just a warning?
duanecwilson
 
Posts: 1
Joined: Wed Sep 26, 2012 3:38 pm
Location: Greenville, SC

Postby Manfred.Castro » Fri Sep 28, 2012 5:08 pm

It's a warning, but if any null data exists in the table already the update will fail.
Manfred Castro
Product Support
Red Gate Software
Manfred.Castro
 
Posts: 209
Joined: Mon Apr 23, 2012 2:49 pm


Return to SQL Compare 10

Who is online

Users browsing this forum: No registered users and 0 guests