All of our databases exist in an environment that will prevent a shadow database being created on the same SQL Server Instance as the development database. And we are using TFS as our Change Automation platform. So would the suggestion be to configure the connection string for the shadow database to use localdb on the TFS server? What if that is not possible?
Comments
1 comment
-
You can customize the connection string for the shadow database to point to any SQL Server instance locally or remotely. You must specify one as the tool need to be able to drop/create the shadow database in order to perform the various operations successfully (import/apply/verify).
More info is available here https://documentation.red-gate.com/sca4/developing-databases/concepts/shadow-database
Add comment
Please sign in to leave a comment.