Activity overview
Latest activity by owen.hall
Hi Robert, Here's the listing as of version 5.3.2. Operations:
UserRequested (a user has told the Clone server to perform an operation)
DispatchedToAgent (the Clone server has told the agent to perform the operation)
Started (the agent has begun working on the operation)
Successful (the operation succeeded)
Faulted (the operation failed)
Canceled (the operation was cancelled before it succeeded or failed)
Images:
BeingCreated (SQL Clone is creating the image)
Created (the image is ready to use)
Missing (more or less unused)
Deleted (the image has been deleted)
BeingDeleted (the image is being deleted)
FailedToCreate (image creation failed)
Clones:
BeingCreated (SQL Clone is creating the clone)
Online (the clone should be available in SQL Server)
Offline (the clone storage exists but we can't online it for some reason)
Missing (the clone storage or data files isn't accessible)
Deleted (the clone has been deleted)
BeingDeleted (the clone is being deleted)
FailedToCreate (clone creation failed)
ImageInaccessible (the clone's host machine can't access its parent image, so we can't risk using it)
CleanUpRequired (we couldn't delete the clone when requested, but will clean it up when we can)
BeingReset (the clone is being reset back to its initial state)
AgentOffline (we don't know the clone's state because we can't contact its agent)
Hope that helps!
/ comments
Hi Robert,Here's the listing as of version 5.3.2.Operations:
UserRequested (a user has told the Clone server to perform an operation)
DispatchedToAgent (the Clone server has told the agent to perf...
SQL Clone agents currently always auto-detect any instances on their local machine, and there isn't any UI support at the moment for removing or unregistering instances that they've discovered. If the instance is actually uninstalled, there might be something quick that can be done - I'd suggest raising a ticket with support before going down that route, though.
/ comments
SQL Clone agents currently always auto-detect any instances on their local machine, and there isn't any UI support at the moment for removing or unregistering instances that they've discovered.If t...
Hi Sugar, There should be no problem with that upgrade from Clone's perspective - naturally we'd recommend taking a backup of the SQL Clone Server's config database (usually SQLClone_Config) beforehand. / comments
Hi Sugar,There should be no problem with that upgrade from Clone's perspective - naturally we'd recommend taking a backup of the SQL Clone Server's config database (usually SQLClone_Config) beforeh...
Hi Gooders, Container support has been on the backburner for 2020, as we've been focusing on extending the product in other directions. It remains on our roadmap (the importance of containerized development is clear), but Clone doesn't currently support it. / comments
Hi Gooders,Container support has been on the backburner for 2020, as we've been focusing on extending the product in other directions. It remains on our roadmap (the importance of containerized dev...
Hi everyone, This was just released for PowerShell in SQL Clone 4.4. We'll be working on adding it to the web UI soon.
There's now a -CompactImage parameter to New-SqlCloneImage. If left unset, it'll default to None (current behaviour - no compaction). Setting it to Compact will shrink the image file after the modifications step, so if you've used modifications to reduce the amount of data in your database and then shrink it (i.e. dropping tables and then running DBCC SHRINKDATABASE), you should find yourself with a smaller image. Image compaction isn't supported on Windows 7 or Server 2008 R2, as the underlying compaction feature is wildly different in performance and reliability on those versions of Windows. Image creation will proceed, but the compaction parameter will be ignored. Thanks! / comments
Hi everyone,This was just released for PowerShell in SQL Clone 4.4. We'll be working on adding it to the web UI soon.
There's now a -CompactImage parameter to New-SqlCloneImage. If left unset, it'l...
Hi Awen, If you have an image made from a SQL Server 2017 database, and clone it into a SQL Server 2019 instance, the 2019 instance will upgrade the clone from 2017 to 2019 on attachment. (The underlying image won't be changed.) I would expect it to work fine, although the upgrade process might make the clone slightly larger than it otherwise would be, due to the changes being written into it.
You'd have more of a problem going the other way - trying to clone a 2019 image into a 2017 server. SQL Server will refuse to downgrade the database from 2019 to 2017, in that situation. Hope that helps!
/ comments
Hi Awen,If you have an image made from a SQL Server 2017 database, and clone it into a SQL Server 2019 instance, the 2019 instance will upgrade the clone from 2017 to 2019 on attachment. (The under...
Hi Gooders, Not in the current version of Clone, but we're actively exploring this space. We're also looking for people to talk to about their expectations and needs for containerised instances - if you'd be open to chatting with us, please send us an email at sqlcloneteam@red-gate.com. Thanks! / comments
Hi Gooders,Not in the current version of Clone, but we're actively exploring this space.We're also looking for people to talk to about their expectations and needs for containerised instances - if ...
Hi Gert, This isn't a situation we've seen before, but Chris's advice is the best course for now. If you need help deleting the file physically, it'd be easiest to raise a support ticket with support@red-gate.com - it should be straightforward enough, but there might be some back-and-forth.
We'll look into adding a way of deleting clones in this state without having to database-dive.
Owen
/ comments
Hi Gert,This isn't a situation we've seen before, but Chris's advice is the best course for now. If you need help deleting the file physically, it'd be easiest to raise a support ticket with suppor...
That's certainly much longer than we'd expect just to unmount. If you see that kind of behaviour again, please feel free to log a support ticket and we'll try to get to the bottom of it. / comments
That's certainly much longer than we'd expect just to unmount. If you see that kind of behaviour again, please feel free to log a support ticket and we'll try to get to the bottom of it.
Hi jakob, Right now, there's no facility for images to shrink when the amount of data inside them is reduced. However, making this possible is a fairly common request, so we intend to tackle this issue fairly soon - probably within the next couple of months. Keep an eye on the release notes! / comments
Hi jakob,Right now, there's no facility for images to shrink when the amount of data inside them is reduced. However, making this possible is a fairly common request, so we intend to tackle this is...