May 31, 2012 at 12:32 pm
I am coping database from 1 server to another server usign backup restore process.
Now i need to enable the file stream feature on primary database, so is there anything i need to change in my backup restore process to apply the filestream feature as well on secondary server.
I am using SQL 2008 SP2 version on both serevr.
Thanks in advance for your help.
June 2, 2012 at 6:31 pm
Yes, filestream has to be enabled at the server level first using SQL Server Configuration Manager. Make sure you enable and configure filestream identically on both servers.
June 2, 2012 at 7:33 pm
Thanks For your response.
I got the error when i am trying to restore the database, so i enabled it on secondary server and restore went fine.
Now i have am facing some other issue when i am trying to converting Blob data to file stream because of my table structure. i have resloved table structure issue and truncated filestream table but still it didn't release space on the drive, so i went ahed and delete those files manually from that filestream folder.
Now when i am trying to insert those records again getting error.
The operating system returned the error '0xc000003a({Path Not Found} The path %hs does not exist.)' while attempting 'NtCreateFile' on 'G:\MSSQL10.MSSQLSERVER\MSSQL\DATA\Filegroupname\dbf02426-8013-4d03-8c44-a60d92d715a1\2e10c5c9-4db2-4223-aeba-5a67601678fd\000055ef-000015a0-0326'. [SQLSTATE 42000] (Error 3634) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.
I thought it is looking the same folder name FSLOG which was still existed on that path.
Again i deleted that folder manully and now i am getting below error.
FILESTREAM data container 'G:\MSSQL10.MSSQLSERVER\MSSQL\DATA\Filegroupname' is corrupted. Database cannot recover. [SQLSTATE HY000] (Error 5535) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.
Can you please guide me for how to delete the data from filestream table??
Thanks inadvance for your help.
June 2, 2012 at 8:47 pm
Don't ever delete files manually. Sounds like you hit a case of a deferred drop operation. When there is a lot to be deleted or truncated, the actual delete may be done later as a background process in small batches. These will show in sys.allocation_units as type = 0 and type_desc = dropped.
My suggestion is to go back to restoring the backup and then start over.
June 11, 2014 at 2:40 am
You need to go with external software which can resolve it accurately.
SSMS Expert
June 11, 2014 at 2:54 am
Elliswhite (6/11/2014)
You need to go with external software which can resolve it accurately.
No, he needs to restore the backup he has.
2 year old thread.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply