Settings and activity

Hi everyone. I have merged some User Voice items on this topic of “filtered” static data, as there was significant overlap. I want to share our current guidance on handling scenarios where you need to version a subset of the columns and/or rows in the table.

With SQL Source control, the best option at this point is to use a post-deployment script for this purpose.

SQL Source Control introduced pre- and post- scripts in v6.3.

A post-deployment script gives you a good amount of flexibility over exactly which rows or columns of data you want to include in your project. Example post-deployment scripts for static data are here: https://documentation.red-gate.com/soc7/common-tasks/working-with-pre-post-deployment-scripts/static-data

If you make heavy use of Static Data, we have stronger support for this in SQL Change Automation.

SQL Change Automation:

• Supports column filtered static data tables in the SCA plugin in SSMS
• Supports multiple post-deployment scripts, in case there is a preference to manage static data tables in dedicated post-deployment scripts
• Allows approaches like bulk loading larger static data tables by supporting SQLCMD variables in migration and post-deployment scripts

If there are other use cases where a migrations approach would add value to the team – such as easily being able to run data modification statements as part of deployments, or being able to customize the TSQL for schema changes – then changing from SQL Source Control to SQL Change Automation might make sense.