RESTORE HEADERLISTONLY and FILELISTONLY do not remove leases when using FROM URL - by Greg Low - Australia

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 869995 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/9/2014 12:01:44 AM
Access Restriction Public


When the RESTORE DATABASE .... FROM URL command is used, it creates an infinite lease on the file in Azure storage and removes the lease when it completes.

The HEADERLISTONLY and FILELISTONLY versions of RESTORE create the lease but do not release it again.
Sign in to post a comment.
Posted by Microsoft on 5/15/2014 at 10:09 AM
Thank you for the feedback. We have identified the problem being a race condition in code. We are working on a fix to be published in later CU.

Since it is a race, running the same command again could get the lease released. That lease won't prevent a data restore command from running and that will actually get the lease released upon finish.