Handle system named column default constraints when importing and generating scripts
When maintaining a database, like to assign names to unnamed default constraints. However, generated script only works if the target database has identically named "unamed" default constraints.
To add robustness to the script, I modify these to a short snippet that works on the schema+table+column. (Using a snippet in SQL Prompt to speed the process :)
But why do I need to do this - after all it is replacing machine generated code?
Here is the SQL Prompt snippet I use: