March 7, 2011 at 8:34 am
Hello all,
I have been a member of this site for awhile now and would first like to thank all of you for having this kind of information available. This is my first time i have posted on here but i have seem to have hit a brick wall when it comes to understanding and resolving this issue and I was hoping someone might be able to assist with this.
Just to give a background on the type of environment I am currently supporting. It is an active, passive, passive node environment (clustered) which is running SQL server 2005 (working on upgrading to 2008) and these DB services are setup to support a Microsoft SharePoint environment which contains 4 web front end servers (clustered as well) 2 Microsoft project servers and an Indexing server.
For the SharePoint environment we have setup, we have sites which sit on content db's and every so often, I will recieve an alert stating that the content db xxx is unreachable (we have multiple content db's so it is never the same one) but when looking back in the event viewer and the logs within the SQL environment, i cannot find any reason why this would throw the error and no issue with the sites which reside on the respective content db would lose connecitivy and would still be functioning normally. I went back and looked into a different environment (similiar setup but using SQL 2008) and they tend to recieve the same error as well, I spoke with the support group for that environment and they provided the following below-
"I found the issue was with the content DBs within Central Admin, in that, these were taken off line when I no longer wanted sites to be added. I found that what I needed to do was keep these “on line” but in turn manage this through number of sites per DB vs. taking offline, i.e. max number of sites is equal to the number of sites currently in that DB."
Unfortunetly, this cannot be the solution to my existing problem due to the fact that we move sites off the content db's when they grow to large or even create new content db's (as per microsoft's best practices)
I hope this all makes sense and i provided enough information for any type of resolution, or even best troubleshooting practices on this.
March 7, 2011 at 9:33 am
Is Autoclose set on the databases?
March 7, 2011 at 11:14 am
Auto close option is set to false on all content db's
March 7, 2011 at 2:07 pm
"Unreachable" is a pretty vague message. It could mean that the DB is offline or it could mean that it's running slow and the connection timed out or it could be a number of other things. Are there any errors in the SQL Server log around the same time as the errors in the Exchange Server? Also check the default trace to see if there is anything in there around the time of the errors, changes to databases or security or status or something.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 9, 2011 at 12:48 pm
Had the error occur today and when researching into it a little bit more, it looked like SP2 was installed on it causing the DB unreachable to generate. I am still waiting for one so i can follow these tips you have provided. I will keep you in the loop to let you know what i find out.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply