Default Ojbects not being created - When Creating New Databases 1

[eb24]

Recently, I noticed that everytime I create a NEW database in SQL Server 2000, not all of the default 'objects' are being created. For example, on previous new databases that I would create, under the Stored Procedures node, there would be a bunch of dt_ stored procedures automatically installed. But recently, ~2 months or so, I have noticed that in the same node, i.e. Stored Procedures, none of the aforementioned objects are being installed. When I click on the node, I notice the message on top 'There are no items to show in this view'. I can still create stored procedures and performance still seems to be the same, but those defaults aren't there.

Does anyone know why this is the case? Is this good/bad? Will it hamper my database later on?

Thank you in advance for any advice on the subject.

 

[JayKusch]

You need to review your Model database. When a new DB is created, the Model DB is used as the template. Thus, if you want certain tables, views, stored procedures ... to be included in each new DB creation, you must add them to the Model DB.

On the flip side ... if there are DB objects you DO NOT want to be included within each new DB creation task, you must remove them from the Model DB.

Thanks

J. Kusch

 

[eb24]

JayKusch:

Thanks for your expeditious response!

I went ahead and read up on this model system database in BOL, but still couldn't find if disabling this option, i.e. of not installing these defaults, is good or not. Does anyone know if this is good/bad or how it affects the newly created database?

 

[eb24]

Oops! I forgot to add that the model database DOES NOT have any stored procedures in there and BOL does talk about it having some.

Is this correct?