Why SCA is creating a shadow db on Azure when clicked on refresh button
catalogdb
Posts: 21 New member
Hi,
When I click on refresh button, SCA is creating a new db in the Azure sql. This is a big concern for me because this is additional cost incurring and forgetting to cleanup this after importing migration scripts will bill additional costs which is not acceptable by the client.
I am unable to understand why SCA is creating shadow database despite of setting "skip creating shadow datbase.." option in the VS project settings. Is it mandatory for SCA to create shadow db on the devopment db? can't it use localdb? How to avoid this unwanted azure billing
When I click on refresh button, SCA is creating a new db in the Azure sql. This is a big concern for me because this is additional cost incurring and forgetting to cleanup this after importing migration scripts will bill additional costs which is not acceptable by the client.
I am unable to understand why SCA is creating shadow database despite of setting "skip creating shadow datbase.." option in the VS project settings. Is it mandatory for SCA to create shadow db on the devopment db? can't it use localdb? How to avoid this unwanted azure billing
Tagged:
Best Answer
-
Ivo_Miller
Posts: 31 Silver 3
Hi,
SQL Chnage Automation always needs a shadow database. By default SQL Change Automation will create the shadow database in the same location as the development database.
You can instead set it to a different location, such as on localdb, by adding a ShadowConnectionString entry in the user settings file. Setting the shadow to be local is indeed recommended if it is possible, as it is likely to perform a bit better.
See https://documentation.red-gate.com/sca/developing-databases/concepts/shadow-database and https://documentation.red-gate.com/sca/reference/sql-change-automation-project-user-settings for more information.
Kind Regards,
Ivo Miller
Ivo Miller
RedGate Software Developer
