Sql-server – Unclosed quotation mark after the character string restoring from Azure blob

A media family has more than one file in it when you stripe your backups. So, if you call your backup like so:

backup log [OurDb] to file = 'c:\file1', file='c:\file2'

In my example, the backup would have been striped across two files (that is to say that half of the backup would have gone to file1 and half to file2) and both files would be needed for a restore. To see what files are needed, take a look at backupmediafamily in msdb. The following query should get you there:

select family_sequence_number, physical_device_name
from backupmediafamily
where media_family_id = (
   select media_family_id
   from backupmediafamily
   where physical_device_name = N'C:\...\diff\backup_2012_12_23_085000_4627006.bak'
)

Then, to restore, you'd have to do something like this for each media family that you want to restore:

restore database [OurDb] from file = ''c:\file1', file='c:\file2', ... with norecovery

Finally, when you're at the point you want to finally bring the database online (i.e. you're done restoring log files), you do:

restore database [OurDb] with recovery

Edited Jan 2016: Possible solution below.

Original Response

For anyone else looking for this the answer appears to be because of "SimpleAD" (http://docs.aws.amazon.com/directoryservice/latest/simple-ad/what_is.html)

SimpleAD is supposed to be a free drop-in replacement for Windows Active Directory, but it looks like there are some differences. Tracked down via this forum post: https://forums.aws.amazon.com/thread.jspa?messageID=633745

Solution: - Replace using SimpleAD with a real version (obviously expensive and a lot of work), OR - Live with it. It appears to be an old bug that won't be fixed quickly, judging by other comments.

Not perfect, but I hope that helps someone if they have the same issues.

Update: Jan 2016

Reading the following has fixed the issue for us:

https://www.suse.com/support/kb/doc.php?id=7016786

In this Microsoft document you will find their suggested workaround. https://support.microsoft.com/en-us/kb/3000850

Here is some of the information from that document.

Workaround To work around this problem, set the value of the ProtectionPolicy registry entry to 1 to enable local backup of the MasterKey instead of requiring a RWDC in the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb

Based in that information, it is obvious that this would need to be done on each Windows 8.1 client that has been updated with KB2992611 or KB3000850.

Appears to works for SQL management studio, but Visual Studio can't attach a process or debug.