Activity overview
Latest activity by ChrisHurley
Thanks for the update! That's really useful to hear about, and I'm glad it's now working. I'll have a look what options we have to prevent others getting into this situation in the future. / comments
Thanks for the update! That's really useful to hear about, and I'm glad it's now working.I'll have a look what options we have to prevent others getting into this situation in the future.
Hm, interesting. This is a problem that we've heard of before with Azure DevOps, but haven't been able to explore properly. We could potentially explore this further with network tracing and/or a private build with some additional logging to see what headers/cookies we're receiving. Could you open a ticket with support@red-gate.com and mention this conversation? / comments
Hm, interesting. This is a problem that we've heard of before with Azure DevOps, but haven't been able to explore properly.We could potentially explore this further with network tracing and/or a pr...
At the moment there isn't a way to persist/copy clone templates between images - they're scoped to a particular image. Also, although we store the filename, we don't store the full path (in particular, we don't have access to it if files are uploaded in the web UI, and it's possible to specify scripts directly without a file in PowerShell too). Therefore the best workflow for now is to maintain the scripts that you want for particular images in a well-known location and to have a script that recreates the image and templates together, using those scripts. You could also use the -Sql parameter of New-SqlCloneSqlScript pass the script to SQL Clone as a string if you want to manage how it's loaded in a different way. Thanks for your feedback about this being a problem! We'll keep that in mind for our future work. / comments
At the moment there isn't a way to persist/copy clone templates between images - they're scoped to a particular image. Also, although we store the filename, we don't store the full path (in particu...
SQL Clone Server uses double-submit cookie verification as a mitigation against cross-site request forgery. Although CSRF is a browser concern, our PowerShell cmdlets and therefore Azure DevOps extension also need to send requests that comply with that contract. This means that requests should have a header and a cookie set to matching values. The cmdlets and therefore extension that uses them sets these to constants. Is there any possibility that the headers or cookies are being transformed/stripped between the Azure DevOps agent and SQL Clone Server, perhaps by a proxy? / comments
SQL Clone Server uses double-submit cookie verification as a mitigation against cross-site request forgery. Although CSRF is a browser concern, our PowerShell cmdlets and therefore Azure DevOps ext...
Hi Jakob, We don't currently have a feature to copy images, but it is possible to rename images in SQL Clone, which can be automated: https://documentation.red-gate.com/clone4/automation/powershell-cmdlet-reference/rename-sqlcloneimage You could use this to maintain a consistent name for the current image, which gets updated when a new image is available (and old images are renamed until their clones are removed and they can be cleaned up). / comments
Hi Jakob,We don't currently have a feature to copy images, but it is possible to rename images in SQL Clone, which can be automated:https://documentation.red-gate.com/clone4/automation/powershell-c...
Hi Ross, Thanks for your feedback! Modification scripts are applied to the image once it's been created, but only to the image, not the source database. It would be safe to use a modification script to truncate the tables, but this probably wouldn't help that much in your situation unfortunately. Because the image is created including all the data before you truncate it, it will still take the same amount of time to create, and the image will also consume unnecessary disk space as it will remain at its largest size (we are considering adding functionality to compact images to address this second issue). SQL Clone operates mostly at the file level, so the workflow that I'd suggest for creating a schema-only image would be to create a blank database and use SQL Compare to compare the source database against it. You can then deploy the schema into the blank database and then use that database to create your image. Hope that's helpful, Chris / comments
Hi Ross,Thanks for your feedback!Modification scripts are applied to the image once it's been created, but only to the image, not the source database. It would be safe to use a modification script ...
Just to follow up on this, we're working on the solution to this but it didn't quite make it in for our release today (3.1.6). However, we're aiming to release a fix for this soon in 3.1.7. / comments
Just to follow up on this, we're working on the solution to this but it didn't quite make it in for our release today (3.1.6). However, we're aiming to release a fix for this soon in 3.1.7.
Hi, I can confirm that a fix that we did recently for another issue (in SQL Clone 3.1.2) has resulted in some problems with handling of batches in transactions - apologies for the inconvenience. We'll aim to get that sorted out for our next release. / comments
Hi,I can confirm that a fix that we did recently for another issue (in SQL Clone 3.1.2) has resulted in some problems with handling of batches in transactions - apologies for the inconvenience. We'...
Hi Ross, If you get all of the images through PowerShell with Get-SqlCloneImage then you should be able to select just the Name properties like this: $images = Get-SqlCloneImage $imageNames = $images.Name<br> The $imageNames variable will then contain the list of image names. / comments
Hi Ross,If you get all of the images through PowerShell with Get-SqlCloneImage then you should be able to select just the Name properties like this:$images = Get-SqlCloneImage$imageNames = $images....
You need to install an agent on any machine where you're either creating images (either directly from a database on the instance, or with a temporary instance you're using to create images from backup) or creating clone databases derived from those images. This is because SQL Clone uses disk-based virtualization technology and so needs to be able to create and mount virtual hard disks (and use the Volume Shadow Copy Service to create images from live databases). So if you want to create clones on machines in your Release environment then you'll need to install agents there. You only need one SQL Clone Server, though - this is the central coordination server from which the agents are controlled. Note that SQL Clone doesn't create images or clones using clustered instances (although you can create images from a backup taken from a cluster using another instance), and that we wouldn't recommend using clone databases for production. / comments
You need to install an agent on any machine where you're either creating images (either directly from a database on the instance, or with a temporary instance you're using to create images from bac...