model db should I make it read-only

What kind of troubles would I get into if I made the
model database read-only? By saying that this database
is only used for retrieving information and is never
gathering or modifying information with update, insert,
or delete operations, making it read-only will eliminate
a lot of overhead and increase its performance is this a
true statement?
Thanks for your input.The proof of the pudding is in the eating. Why not just try it out? After I
set the model database to read only, I get the following error message when
I try to create another database:
Server: Msg 3906, Level 16, State 1, Line 1
Could not run BEGIN TRANSACTION in database 'myTest' because the database is
read-only.
The CREATE DATABASE process is allocating 0.63 MB on disk 'myTest'.
The CREATE DATABASE process is allocating 0.49 MB on disk 'myTest_log'.
And the new database is not created.
Also, even if there is no problem with creting a new database, since the
model database is so tiny and is not used often at all, performance isn't
really an issue.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Rachan Terrell" <web24by7@.hotmail.com> wrote in message
news:22d501c3a92d$5b1ee640$a601280a@.phx.gbl...
> What kind of troubles would I get into if I made the
> model database read-only? By saying that this database
> is only used for retrieving information and is never
> gathering or modifying information with update, insert,
> or delete operations, making it read-only will eliminate
> a lot of overhead and increase its performance is this a
> true statement?
> Thanks for your input.|||Rachan,
The model database is only used by SQL Server as basis to
create new user databases.
It is actually not used for anything else.
Let's say you are going to build 10 different databases
that will have same security, sizing, etc., you can
configure the model database once and all of your
databases will be created with the same configuration.
This will save you lots of time.
Generally, this database is not updated or no one really
uses it. So I do not think you are going to gain any
performance increase by making it read only.
HTH
DeeJay
Please Reply to NewsGroup Only.
>--Original Message--
>What kind of troubles would I get into if I made the
>model database read-only? By saying that this database
>is only used for retrieving information and is never
>gathering or modifying information with update, insert,
>or delete operations, making it read-only will eliminate
>a lot of overhead and increase its performance is this a
>true statement?
>Thanks for your input.
>.
>|||DeeJay,
Thanks for you input. The reason that I want to make the
database read-only is because the database is located on
client PC and they nerver going to use it. I just don't
know what kind of overhead the server is making when it
deal with database if any at all. Can you explain what
kind of overhead the server use with dealing with
database? I could not find any info on the web regarding
this.
Thanks,
Rachan
>--Original Message--
>Rachan,
>The model database is only used by SQL Server as basis
to
>create new user databases.
>It is actually not used for anything else.
>Let's say you are going to build 10 different databases
>that will have same security, sizing, etc., you can
>configure the model database once and all of your
>databases will be created with the same configuration.
>This will save you lots of time.
>Generally, this database is not updated or no one really
>uses it. So I do not think you are going to gain any
>performance increase by making it read only.
>HTH
>DeeJay
>Please Reply to NewsGroup Only.
>>--Original Message--
>>What kind of troubles would I get into if I made the
>>model database read-only? By saying that this database
>>is only used for retrieving information and is never
>>gathering or modifying information with update, insert,
>>or delete operations, making it read-only will
eliminate
>>a lot of overhead and increase its performance is this
a
>>true statement?
>>Thanks for your input.
>>.
>.
>|||Linchi,
Thanks for your input. The model database that we use
here is ship to client PC. Since they will not be using
it (create new database..etc) I through that I might be
able to save some overhead of the server maintain of the
database. Do you know what kind of overhead the server
use when dealing with database?
Thanks,
Rachan
>--Original Message--
>The proof of the pudding is in the eating. Why not just
try it out? After I
>set the model database to read only, I get the following
error message when
>I try to create another database:
>Server: Msg 3906, Level 16, State 1, Line 1
>Could not run BEGIN TRANSACTION in database 'myTest'
because the database is
>read-only.
>The CREATE DATABASE process is allocating 0.63 MB on
disk 'myTest'.
>The CREATE DATABASE process is allocating 0.49 MB on
disk 'myTest_log'.
>And the new database is not created.
>Also, even if there is no problem with creting a new
database, since the
>model database is so tiny and is not used often at all,
performance isn't
>really an issue.
>--
>Linchi Shea
>linchi_shea@.NOSPAMml.com
>
>"Rachan Terrell" <web24by7@.hotmail.com> wrote in message
>news:22d501c3a92d$5b1ee640$a601280a@.phx.gbl...
>> What kind of troubles would I get into if I made the
>> model database read-only? By saying that this database
>> is only used for retrieving information and is never
>> gathering or modifying information with update, insert,
>> or delete operations, making it read-only will
eliminate
>> a lot of overhead and increase its performance is this
a
>> true statement?
>> Thanks for your input.
>
>.
>