Activity overview
Latest activity by tomslickers
SQL Backup without sysadmin
We're trying to get SQL Backup working using an account that is not sysadmin. The account is db_owner in all databases. We added SkipChecks=1 to HKEY_LOCAL MACHINE\Software\Red Gate\SQL Backup\Back...
SQL Clone hangs during image creation
We're having a problem creating an image for one of our databases. The SQL Clone UI provides updates up to "60% Restoring backup" but nothing further after that. We tried upgrading to the latest ve...
Orphaned SQL Clone Images
Today I noticed that there were some "orphaned" SQL Clone images on one of our servers, i.e. the images were still there but they were not listed in the SQL Clone UI. I was able to delete these man...
FYI I got this working by giving the service account running the SQL Backup Agent access to the network share. / comments
FYI I got this working by giving the service account running the SQL Backup Agent access to the network share.
Create Image from Network Backup
Is it possible to create an image from a Red Gate backup on a network share, or do I need to always copy the backup to the server being used to create the image?
Kendra - yes we can make a small database change, especially if we move forward with the creation of a database for this purpose as you have suggested. Thanks for your help with this. / comments
Kendra - yes we can make a small database change, especially if we move forward with the creation of a database for this purpose as you have suggested. Thanks for your help with this.
I am not able to reproduce this behavior. When I commit a post-deployment script to Git, it is not deployed unless I also include a database schema change. / comments
I am not able to reproduce this behavior. When I commit a post-deployment script to Git, it is not deployed unless I also include a database schema change.
Yes. SQL Source Control / State Based + SQL Change Automation. I tried this again just now with the same result.I made a harmless change to my post-deployment script. SQL Source Control listed this on the Commit tab. I committed it to Git and pushed it. My build/deploy process (Jenkins/Octopus) kicked off, but the script artifact in Octopus contains only the following: /* Generated on 24/Apr/2019 10:24 by Redgate SQL Change Automation v3.1.16.3737 This script is empty because the Target and Source schemas are identical. */ / comments
Yes. SQL Source Control / State Based + SQL Change Automation. I tried this again just now with the same result.I made a harmless change to my post-deployment script. SQL Source Control listed thi...
Kendra, Thanks for your detailed and prompt reply. This sounds like a good solution, but I'll still need to make some kind of change to the InstanceConfiguration database so that my pre/post deployment scripts will run. Agree? I suppose this could be a static data change rather than an actual schema change. Tom / comments
Kendra,Thanks for your detailed and prompt reply.This sounds like a good solution, but I'll still need to make some kind of change to the InstanceConfiguration database so that my pre/post deployme...
Need to run post-deployment script without schema change
I'm using post-deployment scripts to deploy SQL Agent jobs and other server-level objects, but the post-deployment script will not run unless there is a database schema change. What's the best way ...