Comments
Sort by recent activity
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 ...
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'...
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 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...
Hi, Data Compare is probably the right tool for this, but it shouldn't have any problems connecting to clone databases (SQL Clone works at the storage level, and this shouldn't affect anything that Data Compare sees). It might be a good idea to get in touch with support@red-gate.com with the error message that you're seeing with Data Compare in order to resolve this. Chris / comments
Hi,Data Compare is probably the right tool for this, but it shouldn't have any problems connecting to clone databases (SQL Clone works at the storage level, and this shouldn't affect anything that ...
Thanks for bringing that to our attention - as you've identified, this is an error and the full text of modification scripts in templates should not be returned. We'll prioritize fixing this for our next release. / comments
Thanks for bringing that to our attention - as you've identified, this is an error and the full text of modification scripts in templates should not be returned. We'll prioritize fixing this for ou...
Hi, Do you know what version you were upgrading from, and does your database use a large number of files (particularly due to FILESTREAM filegroups)? There was a change in 3.1.0 to move a permissions-changing operation that was being done during every clone creation to occur once during image creation, which could cause imaging to be slower but cloning to be faster. The SQL Clone config database itself shouldn't affect the performance of the image or cloning process as it's only used for storing metadata about the system. Thanks, Chris / comments
Hi,Do you know what version you were upgrading from, and does your database use a large number of files (particularly due to FILESTREAM filegroups)? There was a change in 3.1.0 to move a permission...
If you've purchased SQL Clone/Provision then you should have received a serial number on your invoice, and this will also be viewable on the My Products page if you log in with the same Redgate ID you used to activate the product. If you're evaluating, then you can leave that field blank. / comments
If you've purchased SQL Clone/Provision then you should have received a serial number on your invoice, and this will also be viewable on the My Products page if you log in with the same Redgate ID ...