Expected the MSSQL extension (specifically the Schema Compare feature) to preserve the database's default ANSI_NULL setting (which is ON) when generating the publish script. But what actually happened ...