Just verified the finding in SQL Server 2005:
- With MODEL being in READ_ONLY mode, when creating a database using the wizard, it is created read_only. No more changes are possible.
- With MODEL still in READ_ONLY, when creating a database via a SQL script, it is created in read/write mode and tables etc. can be added.
Very interesting behavior--especially given the fact that BOL states one cannot set the MODEL database to READ_ONLY (that's why I did not get my point).