Understood - but this functionality had been in place for a long time, and while I appreciate the move to a reliably generated name, it would have been really helpful to have some way to migrate the old names to the new ones (even a dialect override) - I'm faced with the task of manually finding and dropping hundreds of "old" constraints and then using SchemaUpdate to update the constraints (since some have been changed - additional cols added to some unique constraints etc.) as well as fixing the names. While Steve Ebersole very kindly pointed out that this is an unsupported tool, it's highly useful in the dev process and is widely used early in the dev process.