When the option to insert a values clause with default values for an INSERT statement is in force, the default values used by SQL prompt ignore nulls. e..g if your table is CREATE TABLE foo (bar int NULL) and you let SQL Prompt build an INSERT with default values, it uses 0 as the default for column bar. This is wrong. The true default is NULL. It would be better if SQL Prompt just used a value clause like :

VALUES (DEFAULT)

and let SQL Server figure out the default. Worse yet, check out this table and the generated code:

CREATE TABLE #foo (bar int NOT NULL DEFAULT 42)

INSERT INTO #foo
(
bar
)
VALUES
(0 )

SQL Prompt ignores the defined default value