It’s not SharePoint. It’s SQL.
So this isn’t news to my SharePoint friends out there – SharePoint can’t exist without SQL. When there’s a problem with SQL, there’s definitely a problem with SharePoint. Here’s a quick real-world scenario that most of us have seen at least once or twice:
How did the issue present itself? à "Cannot connect to the configuration database"
Isolating the issue à The error message pretty much sums it up!
Root Cause à SQL server was offline.
Resolution à SQL server was rebooted.
Here are a couple of other common SQL-related issues:
- Users cannot add or edit content on their SharePoint site. This usually means either the database capacity is not sufficient (database size is 50GB and the capacity is 50GB, for example) or there is no room for the transaction logs on the disk drive where the logs are stored.
- Uploading documents takes longer than expected, or users are reporting general slowness. By default, the database file growth is set to grow by 1 MB at a time. Each time the database grows it must lock the database for all users. Pre-growing the database or setting the database auto-growth to a higher value can dramatically improve upload performance.
How can these problems be avoided?
- Check out this great Technet article: Best practices for SQL Server 2008 in a SharePoint Server 2010 farm
- Make the SQL DBA your BFF!