I just ran in to an issue last night that a nightly process made mass changes to a cloned database and caused 150GB of data changes and filled up the hard drive the cloned file was on. It took me almost an hour to troubleshoot this as SQL Clone web interface only showed the Clone as disconnected. The log file only showed errors connecting to the VHD and the same was in the SQL error log. That truly is not the case, the file was on the disk and accessible. It was the fact the drive was full and the VHD could not grow. I would suggest maybe being able to properly report disk space issues to help identify issues.
Comments
2 comments
-
You're right, that's something that our monitoring doesn't pick up at the moment, and SQL Server ends up experiencing errors because it's unable to write. Thanks, I'll add improving that experience to our backlog. -
Plus a bunch to this request.
Add comment
Please sign in to leave a comment.