I've got a small issue with the way AutoSPInstaller creates the config DB. This usually happens as follows:
- Check of DB exists
- Create DB
- Check for max degree of parallelism to be 1
The problem is that, when max degree of parallelism hasn't been configured properly, the script fails. When the setting has been corrected and the script is re-run, the script will fail again as the DB already exists.
It's a lot more logical to check for the max degree of parallelism before creating the DB, as this series of events is pretty messy for a production SQL server when it occurs. DBA's don't like to delete databases.
Is this choice of design due to technical limitations? Or can this be improved?