September 28, 2016 at 7:11 am
I've been banging my head on this one all morning so far, and gotten nowhere.
I'm trying to restore a copy of a database with a Filestream-enabled table which has a Full Text index on it. When the restore runs (Dev workstation, Windows 10, SQL 2014) the restore fails with an OS error 32, the file is in use by another process. There's no AV on this PC (except possibly Windows Defender, which I've not checked to see if it's been disabled.) I am using the MOVE option to put the filestream and data files (MDF / LDF) in locations that exist on the PC, and to which the SQL Server service account has Full Control.
I did try a partial restore, only attempting to restore the Primary filegroup, this did work and got at least the MDF / LDF restored. When I try to restore the filestream filegroup, I go right back to the error 32. The restore process is at least getting started, as the folder inside the Filestream folder for the DB is there, and if I browse into it there are some files (doing this after the restore fails.)
I did, due to the size of the filestream, try creating a striped backup (3 files,) and am currently in the process of re-backing up to one big backup file. I am not hopeful this is going to work.
I also checked, and the PC we are restoring too, does have sufficient space for the database and filestream.
Any thoughts, suggestions, ideas?
I've Googled for ideas this morning, and while I've found a few ideas, none have panned out.
September 28, 2016 at 12:55 pm
September 28, 2016 at 1:51 pm
DeWayne_McCallie (9/28/2016)
https://support.microsoft.com/en-us/kb/3153836
That could be the problem then. This is on a developers stand-alone which I have no control over the patch level of the SQL he has installed. I'll pass along the KB link to him, see what we find.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply