Comments
Sort by recent activity
Hi again - SQL Clone 3.0.7 has just been released, and should fix this issue for you. / comments
Hi again - SQL Clone 3.0.7 has just been released, and should fix this issue for you.
Thanks! That ought to be fine. Best bet is to check the application event log for errors, in that case. You can access that by hitting Win-R and running eventvwr, then accessing Windows Logs, and Application. Look for anything under the SQL Clone Server Setup source. / comments
Thanks! That ought to be fine. Best bet is to check the application event log for errors, in that case. You can access that by hitting Win-R and running eventvwr, then accessing Windows Logs, and A...
Hi ravi, Thanks for bringing this to our attention. There might be some more detail (including the nature of the error) about this issue in your machine's application event log. Could you tell us which version of SQL Clone you're trying to install? Thanks! Owen / comments
Hi ravi,Thanks for bringing this to our attention. There might be some more detail (including the nature of the error) about this issue in your machine's application event log.Could you tell us whi...
Hi Robb, There's an installer available from your SQL Clone server UI that will install the PowerShell cmdlets you need. You can download it from: http://your-sql-clone-server:14145/settings/powershell If you run the installer, close any open PowerShell windows, then open one up again, the cmdlets should be available. Hope that helps! Owen / comments
Hi Robb,There's an installer available from your SQL Clone server UI that will install the PowerShell cmdlets you need. You can download it from:http://your-sql-clone-server:14145/settings/powershe...
Hi! While not directly supported in-tool, it shouldn't be too difficult to move image files from one place to another, then update the SQL Clone config database to refer to the new location. If you'd like to pursue this, probably the simplest option is to get in touch with support@red-gate.com and we can figure this out properly. It's a different story for any existing clones of those images, though. Clone disk files are parented to a specific file path (i.e. pointing straight at the image file), and have that information written directly into them. This is the nature of the VHD file format. It won't be easy to point those at the new image location (you'd need to hack the clone files with a hex editor) - far easier to drop the clones and recreate them afresh once the images have been moved. Hope that helps! Owen / comments
Hi!While not directly supported in-tool, it shouldn't be too difficult to move image files from one place to another, then update the SQL Clone config database to refer to the new location. If you'...
Hi gemu, You can enter your license key via the 'SQL Clone Server Setup' tool installed alongside the SQL Clone server and available from the Start menu (use the 'Manage license...' button in the tool), or, on the web UI, on the Settings/Licensing page. Owen / comments
Hi gemu,You can enter your license key via the 'SQL Clone Server Setup' tool installed alongside the SQL Clone server and available from the Start menu (use the 'Manage license...' button in the to...
Hi Randy, As you'll know, clones are differencing disks, and will grow when something writes to their data files. The usual culprit is SQL Server, which makes its own decisions about what to write to attached data files, and when. That can make diagnosing these kinds of issues tricky. I've got a few diagnostic questions:
Do clones grow on their own if you don't write to them? (E.g. they're just created, with no modification template, and are left to sit there.)
Do clones grow on their own if they're made from images without any modifications?
If you've been seeing growth in clones based on an image from a live database, what about clones based on an image from a backup file? (Or vice versa if you've been making images from backup files?)
Do you have any clones that don't grow by themselves? Is there any pattern there?
Thanks! Owen / comments
Hi Randy,As you'll know, clones are differencing disks, and will grow when something writes to their data files. The usual culprit is SQL Server, which makes its own decisions about what to write t...
Hi David, How about something like this? # download a single use agent installer
<br><div>Invoke-WebRequest `
-Uri http://your.sqlclone.server:14145/api/installer `
-OutFile 'C:\My\Downloads\SingleUseSQLCloneAgentInstaller.exe' `
-UseDefaultCredentials</div><div>
<br># run silent installation
</div><div>C:\My\Downloads\SingleUseSQLCloneAgentInstaller.exe -s `
SERVICEUSERNAME=DOMAIN\Username `
SERVICEPASSWORD=MyPassword</div>
Many thanks! / comments
Hi David,How about something like this?# download a single use agent installer
<br><div>Invoke-WebRequest `
-Uri http://your.sqlclone.server:14145/api/installer `
-OutFile 'C:\My\Downloads\SingleUs...
Thanks for your help with us on this ticket! We've added a new troubleshooting page to help people in future. Owen / comments
Thanks for your help with us on this ticket! We've added a new troubleshooting page to help people in future.Owen
Hi Gert, We've made a change to how we use VSS in our latest release (2.6.3). It might be worth retrying with that version - let us know if that doesn't help! Owen / comments
Hi Gert,We've made a change to how we use VSS in our latest release (2.6.3). It might be worth retrying with that version - let us know if that doesn't help!Owen