We attempted to rename a column in the SQL Change Automation Pre-Deployment script, but it looks like the final script that SQL Change Automation generates for the migration is based on the old column names and not on the new column names that were changed in the Pre-Deployment script. Is there a recommended approach for renaming a column? Does this rename have to happen on the target database before SQL Change Automation is run since it looks like Smart Rename just generates a script that is be run against the target database?
Comments
1 comment
-
Hi @Jim_Brown_VR
The recommended approach would be to rename the column in your development database, then proceed to generate the migration script, and either using PowerShell or one of the add-ons you would then deploy those changes into your target database.
Hope this helps!
Add comment
Please sign in to leave a comment.