MSSQL new DB creation weirdness

When I create a new DB in SQL server 2000, I noticed that the new DB is a reflection of the model DB, but my model db is 5MB in size so all new DB will be 5MB even if theres no data on them.

Ok, I won't change any of the tables in model as I just noticed it holds quite alot of necessary info, as a matter of fact I won't change any of the model data, but I would like it to be of a reduced size as 5MB is too much.

Edited by theSCIENTIST - 16 October 2006 at 5:36pm

Well you want to have space available, depending on what info the db is going to hold. If your space available is little it needs to expand the data file every time you insert data, which makes the whole process slow.
As you appear to be under some kind of weird space constraints, all you can do is trial-error. I have never dealt with such small file (requirements)
As far as the options you mentioned go:
Auto update statistics: For simple DB's you can disable that. Essentially, it can enhance performance on queries thus you can always create statistics manually if required.
Torn page detection: I would leave that on

sql-server-performance.com wrote: If you are worried about getting torn pages in your SQL Server databases, you can have SQL Server tell you if they occur. There is a database option called "torn page detection" that can be turned on and off at the database level. Each database must be set separately. Keep in mind that this option does not prevent torn pages; it only tells you if you have one. Once it discovers one, your database is marked as corrupt, and you have little choice but to restore your database with your latest backup.

Auto Shrink I would turn off, see over time how often they need shrinking.