Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 Databases Inaccessible

Author  Topic 

ChristopherTrumbla
Starting Member

1 Post

Posted - 2011-10-13 : 12:43:28
I've recently moved my MDF and LDF files to our NAS and when you go to the database properties the files are at \\myip\dir.

About a week after doing this I started to see errors in my app that it can't connect to the databases. Upon looking at Management Studio, whenever I tried to expand any of my databases I received an error that the database was inaccessible.

I'm also seeing the below errors in the Event Viewer.

fcb::close-flush: Operating system error (null) encountered.

The log for database 'Search_Service_Application_CrawlStoreDB_c0581e0bd4ee4b91985cd5e1312b296a' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

The only way I have of fixing this is to restart the SQL service or manually take each db offline and online again.

Anyone seen this before and know of a solution?

Thanks,
Christopher

Jon G
Starting Member

31 Posts

Posted - 2011-10-14 : 05:03:10
I have exactly the same problem but for a different reason. I have been running a database on SQL 2005 express Advanced on Server 2003 for a number of years with no problems whatsoever. I have now migrated the database to SQL 2008 express Advanced on Server 2008 and I have to restart the SQL service virtually everyday because the database become unavailable in exactly the way you describe in your post.

It would be good to find a solution

thanks

Jon
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2011-10-14 : 10:36:08
It is bad idead to put DB files in NAS.Minor clutches on network can make your database unavailable.
Go to Top of Page

Jon G
Starting Member

31 Posts

Posted - 2011-10-16 : 11:15:38
Without speaking too soon, I think I may have found the answer to the problem. When I looked at the properties of the database in 2005 it had "Autoclose" switched "OFF". After I had migrated it to SQL 2008 for some reason "Autoclose" was switched "ON". So I have changed it to "OFF" and will monitor it over the next few days and report back.
Go to Top of Page

Jon G
Starting Member

31 Posts

Posted - 2011-10-18 : 12:12:35
It's been 4 days now since I switched off "Autoclose" and all databases have remained accessible without problems so that seems to have fixed it for me!
Go to Top of Page
   

- Advertisement -