官方供應商
我們作為官方授權經銷商，直接提供超過200家開發廠家所發行超過1000個的產品授權給您。
請參閱我們所有的品牌。
SQL Clone v2.3.x
添加對使用 FILESTREAM 或記憶體優化表創建資料庫的圖像和克隆的支援。
11月 6, 2017
新產品
特性
- Machines that no longer exist, but still had clones, can now be removed from SQL Clone by passing the
-Forceparameter to theRemove-SqlCloneMachinecmdlet. - A warning is now given when choosing to create an image using a local path rather than a UNC path, as it will be inaccessible from other machines.
- Machines with agents can now be removed from SQL Clone using the
Remove-SqlCloneMachinecmdlet, once all images and clones created by that machine have been deleted, and the agent is no longer connected to SQL Clone - Uses new Redgate installer
- Get-SqlCloneImageLocation cmdlet creates new image location if it does not exist.
- Added support for creating images and clones of databases using FILESTREAM or memory-optimized tables.
修補程式
- Fixed a failure loading the UI when agents are assigned to environments.
- Fixed a concurrency issue with image monitoring.
- Notification that an agent has failed to update now disappears once the agent has been updated.
- Prevented a cause of agent crashes which could happen immediately after updating SQL Clone Server.
- Fixed an issue preventing clean-up of clones deleted from outside SQL Clone.
- Fixed a web UI inconsistency when creating images via Powershell ('agent is not compatible with this image').
- Fixed an issue where a FullyQualifiedDomainName field was not being correctly parsed.
- Fixed an issue where a 'checking access to this instance' spinner failed to disappear.
- Fixed error which could occur when creating many clones in parallel
- If you delete a clone or image when the SQL Clone Agent is offline, the operation fails instead of being stuck in progress
- You can now successfully delete a clone when the image is unavailable
- Web UI will no longer fail to load if information about when an image or clone was created is missing
- Fixed issue with monitoring image files on non-Windows fileshares.
