I'm using SQL Server 2012 SP2 to backup my transaction logs directly into Azure Blob Storage using the
BACKUP TO URL statement.
I am then attemtpting to verify my transaction log as follows:
RESTORE VERIFYONLY FROM URL = 'https://mystore.blob.core.windows.net/logfile.trn' WITH CREDENTIAL = 'azurecreds'
RESTORE VERIFYONLY operation puts a lease on the file in Azure which I can see using Azure Management Studio's blob browser (The last 2 I created without running RESTORE VERIFYONLY).
I can manually break the lease using Azure Management Studio but am I doing something wrong with
RESTORE VERIFYONLY that is leaving an active lease on the file?