Comments
Sort by recent activity
Thanks! Two ideas for you:
If you pass in an invalid image name, an error is generated. You can start the script with an $ErrorActionPreference = 'Stop', which will stop the script on the first error.
Right now, Get-SqlCloneImage is generating an error and setting $image to $null. If you pass in $null for the -Image parameter to Get-SqlClone, Get-SqlClone will return all of the clones, which is the behavior you're seeing. You can do an if ($null -eq $image) { return } right after the call to Get-SqlCloneImage, which will also save you from grabbing all the clones.
/ comments
Thanks! Two ideas for you:
If you pass in an invalid image name, an error is generated. You can start the script with an $ErrorActionPreference = 'Stop', which will stop the script on the first e...
Would it be possible to see your script? I'm curious why it deleted all clones. / comments
Would it be possible to see your script? I'm curious why it deleted all clones.
Awen, We have a similar upgrade scenario, and I actually set up some VMs and ran some tests to see how SQL Clone would behave between SQL Server 2017 and SQL Server 2019. I can verify what Owen says. In general, cloning a 2017 database onto a 2019 server instance works just fine. Cloning a 2019 database onto a 2017 server instance fails. The waters get a bit muddied if you change the version of the server instance used to generate the clone image. Basically, you can't take a 2017 database, image it on a 2019 server instance, and clone it to a 2017 server instance. I hope that all makes sense and helps in your decision making. / comments
Awen,We have a similar upgrade scenario, and I actually set up some VMs and ran some tests to see how SQL Clone would behave between SQL Server 2017 and SQL Server 2019. I can verify what Owen say...