I can reproduce the problem in both SQL 2008 R2 and SQL 2005 SP3

I have read in several places that default settings for a new db should be based on...