Question ported from Serverfault as it is specific to database maintenance for SharePoint administrators:
For SharePoint administrators, SQL Server is often a black box that is installed as a prerequisite during the SharePoint installation process. As a result, there is very little (if any) planning that goes into the SQL side of the installation, leading to problems that surface somewhere further upstream.
- Transaction Logs that fill drives
- No maintenance plans (or uninformed ones, such as plans that both reorganize and rebuild the indexes)
- Unmanaged autogrowth
- Databases and logs on the same spindles
- Poorly chosen RAID levels
- No backup (or recovery plan)
So... what types of problems do SharePoint administrators without any SQL/DBA experience tend to hit, and what resources would best help an "accidental DBA" get up to speed on SQL planning, administration and performance tuning basics?