Deploy static data in commit order
Static data should be deployed in commit order rather than at the end of the deployment script.
It is currently impossible to write a migration script which depends on static data as the static data will not exist at the point the migration script runs. The migration script can't insert the static data it needs as deployment will then fail later when inserting the new static data which now already exists.
AdminKendra (Product Manager, Redgate) commented
I believe this suggestion is no longer applicable due to changes in the last year.
My understanding is that this suggestion is specific to SQL Source Control project which are deployed with SQL Change Automation.
From SQL Source Control v7 forward, using migrations scripts in SQL Change Automation is the recommended and supported method for implementing a migrations based deployment approach as part of Redgate's Database DevOps solution.
I am going to set the public status of this as 'declined' as we no longer recommend using the legacy migrations feature in SQL Source Control.
Thanks very much for this feedback, and please do let me know if I've misunderstood this request in some way.
If I could vote for this 1000 times, I would. Seems like a huge oversight in terms of deployment and CD practices. Can’t really automate anything without this enhancement...
Chris Michael commented
I have run across this problem too, it would be very useful if this could be done or at least give the option to deploy in standard or commit order.