Database deployment - Environment specific static data

paraggadkari

We have some sort of static data (system configuration table) which is specific to each environment. Let us say, we have remote systems URL configured in a configuration table. The URLs are specific to the environment (a url for QA, UAT and PROD). The current feature only allows static data or migration scripts. Can this be handled using static data feature?

Or is there any way we can attach a package of post-deployment sql scripts which can be picked up by the DM and applied to the DB?

paraggadkari

Never mind. I found the answer under powershell topic.