What I recognized in the field of SharePoint Server implementations, is a lack of affinity for SQL-Server Maintenance. SQL-Server is too much of a black box for most of the SharePoint Admins, and although SQL-Optimization is covered quite well at TechNet it is not seen as essential until users complain.
But it could be very easy, as there is a set of great SQL-Scripts by Ola Hallengren ([http://ola.hallengren.com/](http://www.example.com)) which are perfect for not running into performance issues soon after settting up SharePoint.
It would absolutely make sense to integrate these into AutoSPinstaller.
Still, if it won´t, hope this info will help a lot of you struggling with the absence of a true SQL DBA.
Comments: ** Comment from web user: brianlala **
But it could be very easy, as there is a set of great SQL-Scripts by Ola Hallengren ([http://ola.hallengren.com/](http://www.example.com)) which are perfect for not running into performance issues soon after settting up SharePoint.
It would absolutely make sense to integrate these into AutoSPinstaller.
Still, if it won´t, hope this info will help a lot of you struggling with the absence of a true SQL DBA.
Comments: ** Comment from web user: brianlala **
While I agree this could be useful, it's completely out-of-scope - for the same reason I don't include the SQL installation as part of AutoSPInstaller. I purposely avoid cramming too much in as it multiplies the number of ways the install could break :)
Also, often the account installing SharePoint won't have sysadmin rights to the SQL instance, making it difficult to perform any post-configuration on SQL using AutoSPInstaller.
Brian