Comments
Sort by recent activity
Thank you for reporting the issue and sorry for the inconvenience. We'll fix this asap. Thanks / comments
Thank you for reporting the issue and sorry for the inconvenience. We'll fix this asap. Thanks
By default SQL Source Control run that script to show which objects has changed in the object explorer. You can disable this option if you want or adjust the polling frequency in the Options dialog. [image] / comments
By default SQL Source Control run that script to show which objects has changed in the object explorer. You can disable this option if you want or adjust the polling frequency in the Options dialog.
The missing "Manually Edit the Script" link was a known bug. It was fixed in version 7.0.46.9898 / comments
The missing "Manually Edit the Script" link was a known bug.It was fixed in version 7.0.46.9898
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 / comments
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 d...
I am not aware of any argument you can provide to get the behavior you expect. The last option you suggest can be achieved using a pre-script but I would be very concerned to drop production unintentionally. So I suggest the second option of adding an extra step to drop the database before calling SCA. Add this extra step only when you deploy to transient environments. / comments
I am not aware of any argument you can provide to get the behavior you expect.The last option you suggest can be achieved using a pre-script but I would be very concerned to drop production uninten...