Modifing the Model DB

Could anyone please advise how to modify the location of
the datafile and logfile of the model database?
I need to change them from drive C to drive D.
Thank you.Hi Nathalie,
See the following knowledge base article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224071
--
Jacco Schalkwijk MCDBA, MCSD, MCSE
Database Administrator
Eurostop Ltd.
"Nathalie" <nathalbr@.cellcom.co.il> wrote in message
news:7e5701c35a7f$5742ae00$a001280a@.phx.gbl...
> Could anyone please advise how to modify the location of
> the datafile and logfile of the model database?
> I need to change them from drive C to drive D.
> Thank you.sql

Model DB problem..

attempted to move my Model and msdb database files to a different drive on the server. I did the following:
* Restarted SQL Server 2K with the -T3608 startup parameter
* successfully detached msdb and model DBs
* moved the msdbdata.mdf, msdblog.ldf, model.mdf and modellog.ldf
files to their new homes
* successfully reattached model and msdb

When I take away the -T3808 startup parameter and restart SQL Server, I do not see the model database in the db list in enterprise manager eventhough my 'attach' seemed to work. Now I get the following error when i try and query against the Model database using query analyzer:

"Could not locate entry in sysdatabases for database 'model'. No entry found with that name. Make sure that the name is entered correctly"

Also, when I look in the sysaltfiles table in Master, I see no reference whatsoever to the Model DB

What did I do wrong?attempted to move my Model and msdb database files to a different drive on the server. I did the following:
* Restarted SQL Server 2K with the -T3608 startup parameter
* successfully detached msdb and model DBs
* moved the msdbdata.mdf, msdblog.ldf, model.mdf and modellog.ldf
files to their new homes
* successfully reattached model and msdb

What did I do wrong?

Ouch! I HATE it when that happens. Here's a link, you've probably already read it (here (http://support.microsoft.com/default.aspx?scid=kb;en-us;224071)).

I would (in more or less this order):
1. Look carefully at the SQL Error log
2. Restart with -T3608 and attempt to re-attach model
3. Restore model from a backup (you did have a backup, right?)

I seem to recall from a distant memory that when you moved msdb and model, there was a particular sequence (one HAD to be done before the other). [Edit: here it is, smack in the middle of the link above].

Note If you are using this procedure together with moving the msdb
and model databases, the order of reattachment must be model first
and then msdb. If msdb is reattached first, it must be detached and
not reattached until after model has been attached.

I can't tell for certain from the steps you outline above which you did first.

I have used this procedure to move model, master, msdb and tempdb on several different occasions with no trouble at all (sorry, that doesn't help you, but I did want to verify that the steps outlined above DO work). As I recall, I usually make it a point to move msdb and model in separate steps (restarting SQL Server in between moving these two dbs).

Best of luck,

hmscottsql

model database "lost"

When moving the sysdatabases to a different drive using specific Q224071 ()
instructions i found that the model db does not show up and when running:
use model
go
sp helpfile
go
i get:
Could not locate entry in sysdatabases for database model. No entry found
with that name. Make sure that the name is entered correctly.
any ideas?Did you enable trace flag 3608 and reattach model database before msdb?
The proper steps are:
1. moving master
2. moving model
3. moving msdb
4. moving tempdb
-oj
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> When moving the sysdatabases to a different drive using specific Q224071
> ()
> instructions i found that the model db does not show up and when running:
> use model
> go
> sp helpfile
> go
> i get:
> Could not locate entry in sysdatabases for database model. No entry found
> with that name. Make sure that the name is entered correctly.
> any ideas?
>|||Hi,
Was sp_attach_db statement successfull? And did you try to remove -T3608
flag from the startup parameter?
If you have done the above, try to re-start the server and see what the
error log has to say.
Thanks
Yogish|||In addition tot he other posts, check the dbid for model (in sysdatabases).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in mess
age
news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> When moving the sysdatabases to a different drive using specific Q224071 (
)
> instructions i found that the model db does not show up and when running:
> use model
> go
> sp helpfile
> go
> i get:
> Could not locate entry in sysdatabases for database model. No entry found
> with that name. Make sure that the name is entered correctly.
> any ideas?
>|||flag 3608 yes, it was enabled.
About the steps you mentioned, i followed Q224071 and it has the order like
these:
1. moving msdb
2. moving master
3. moving model
4. moving tempdb
Could you confirm where you got your order?
"oj" wrote:

> Did you enable trace flag 3608 and reattach model database before msdb?
> The proper steps are:
> 1. moving master
> 2. moving model
> 3. moving msdb
> 4. moving tempdb
>
> --
> -oj
>
> "Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
> message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
>
>|||No attach wasnt successful. End up with error:
Could not locate entry in sysdatabases for database model. No entry found
with that name. Make sure that the name is entered correctly.
"Yogish" wrote:

> Hi,
> Was sp_attach_db statement successfull? And did you try to remove -T3608
> flag from the startup parameter?
> If you have done the above, try to re-start the server and see what the
> error log has to say.
> --
> Thanks
> Yogish|||Make sure you attached them in the right order, I had a similar issue where
msdb became model (as well as msdb) because of a typo when attaching the
model database, led to some odd behaviour :-)
Life without model
http://www.sqlteam.com/item.asp?ItemID=10060
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> When moving the sysdatabases to a different drive using specific Q224071
> ()
> instructions i found that the model db does not show up and when running:
> use model
> go
> sp helpfile
> go
> i get:
> Could not locate entry in sysdatabases for database model. No entry found
> with that name. Make sure that the name is entered correctly.
> any ideas?
>|||It's clearly stated that model must be attached before msdb in kb 224071.
The actually order for master/tempdb is not that important when you're
moving system databases.
Moving the MSDB database (SQL Server 2000)
Note If you are using this procedure in conjunction with moving the msdb and
model databases, the order of reattachment must be model first and then
msdb. If msdb is reattached first, it must be detached and not reattached
until after model has been attached.
-oj
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
message news:C3F4F8D7-135E-4113-9423-92566B6BE454@.microsoft.com...[vbcol=seagreen]
> flag 3608 yes, it was enabled.
> About the steps you mentioned, i followed Q224071 and it has the order
> like
> these:
> 1. moving msdb
> 2. moving master
> 3. moving model
> 4. moving tempdb
> Could you confirm where you got your order?
> "oj" wrote:
>

model database "lost"

When moving the sysdatabases to a different drive using specific Q224071 ()
instructions i found that the model db does not show up and when running:
use model
go
sp helpfile
go
i get:
Could not locate entry in sysdatabases for database model. No entry found
with that name. Make sure that the name is entered correctly.
any ideas?Did you enable trace flag 3608 and reattach model database before msdb?
The proper steps are:
1. moving master
2. moving model
3. moving msdb
4. moving tempdb
-oj
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> When moving the sysdatabases to a different drive using specific Q224071
> ()
> instructions i found that the model db does not show up and when running:
> use model
> go
> sp helpfile
> go
> i get:
> Could not locate entry in sysdatabases for database model. No entry found
> with that name. Make sure that the name is entered correctly.
> any ideas?
>|||Hi,
Was sp_attach_db statement successfull? And did you try to remove -T3608
flag from the startup parameter?
If you have done the above, try to re-start the server and see what the
error log has to say.
--
Thanks
Yogish|||In addition tot he other posts, check the dbid for model (in sysdatabases).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in message
news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> When moving the sysdatabases to a different drive using specific Q224071 ()
> instructions i found that the model db does not show up and when running:
> use model
> go
> sp helpfile
> go
> i get:
> Could not locate entry in sysdatabases for database model. No entry found
> with that name. Make sure that the name is entered correctly.
> any ideas?
>|||flag 3608 yes, it was enabled.
About the steps you mentioned, i followed Q224071 and it has the order like
these:
1. moving msdb
2. moving master
3. moving model
4. moving tempdb
Could you confirm where you got your order?
"oj" wrote:
> Did you enable trace flag 3608 and reattach model database before msdb?
> The proper steps are:
> 1. moving master
> 2. moving model
> 3. moving msdb
> 4. moving tempdb
>
> --
> -oj
>
> "Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
> message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> > When moving the sysdatabases to a different drive using specific Q224071
> > ()
> > instructions i found that the model db does not show up and when running:
> > use model
> > go
> > sp helpfile
> > go
> >
> > i get:
> > Could not locate entry in sysdatabases for database model. No entry found
> > with that name. Make sure that the name is entered correctly.
> >
> > any ideas?
> >
>
>|||No attach wasnt successful. End up with error:
Could not locate entry in sysdatabases for database model. No entry found
with that name. Make sure that the name is entered correctly.
"Yogish" wrote:
> Hi,
> Was sp_attach_db statement successfull? And did you try to remove -T3608
> flag from the startup parameter?
> If you have done the above, try to re-start the server and see what the
> error log has to say.
> --
> Thanks
> Yogish|||Make sure you attached them in the right order, I had a similar issue where
msdb became model (as well as msdb) because of a typo when attaching the
model database, led to some odd behaviour :-)
Life without model
http://www.sqlteam.com/item.asp?ItemID=10060
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> When moving the sysdatabases to a different drive using specific Q224071
> ()
> instructions i found that the model db does not show up and when running:
> use model
> go
> sp helpfile
> go
> i get:
> Could not locate entry in sysdatabases for database model. No entry found
> with that name. Make sure that the name is entered correctly.
> any ideas?
>|||It's clearly stated that model must be attached before msdb in kb 224071.
The actually order for master/tempdb is not that important when you're
moving system databases.
Moving the MSDB database (SQL Server 2000)
Note If you are using this procedure in conjunction with moving the msdb and
model databases, the order of reattachment must be model first and then
msdb. If msdb is reattached first, it must be detached and not reattached
until after model has been attached.
--
-oj
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
message news:C3F4F8D7-135E-4113-9423-92566B6BE454@.microsoft.com...
> flag 3608 yes, it was enabled.
> About the steps you mentioned, i followed Q224071 and it has the order
> like
> these:
> 1. moving msdb
> 2. moving master
> 3. moving model
> 4. moving tempdb
> Could you confirm where you got your order?
> "oj" wrote:
>> Did you enable trace flag 3608 and reattach model database before msdb?
>> The proper steps are:
>> 1. moving master
>> 2. moving model
>> 3. moving msdb
>> 4. moving tempdb
>>
>> --
>> -oj
>>
>> "Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
>> message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
>> > When moving the sysdatabases to a different drive using specific
>> > Q224071
>> > ()
>> > instructions i found that the model db does not show up and when
>> > running:
>> > use model
>> > go
>> > sp helpfile
>> > go
>> >
>> > i get:
>> > Could not locate entry in sysdatabases for database model. No entry
>> > found
>> > with that name. Make sure that the name is entered correctly.
>> >
>> > any ideas?
>> >
>>

model database "lost"

When moving the sysdatabases to a different drive using specific Q224071 ()
instructions i found that the model db does not show up and when running:
use model
go
sp helpfile
go
i get:
Could not locate entry in sysdatabases for database model. No entry found
with that name. Make sure that the name is entered correctly.
any ideas?
Did you enable trace flag 3608 and reattach model database before msdb?
The proper steps are:
1. moving master
2. moving model
3. moving msdb
4. moving tempdb
-oj
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> When moving the sysdatabases to a different drive using specific Q224071
> ()
> instructions i found that the model db does not show up and when running:
> use model
> go
> sp helpfile
> go
> i get:
> Could not locate entry in sysdatabases for database model. No entry found
> with that name. Make sure that the name is entered correctly.
> any ideas?
>
|||Hi,
Was sp_attach_db statement successfull? And did you try to remove -T3608
flag from the startup parameter?
If you have done the above, try to re-start the server and see what the
error log has to say.
Thanks
Yogish
|||In addition tot he other posts, check the dbid for model (in sysdatabases).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in message
news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> When moving the sysdatabases to a different drive using specific Q224071 ()
> instructions i found that the model db does not show up and when running:
> use model
> go
> sp helpfile
> go
> i get:
> Could not locate entry in sysdatabases for database model. No entry found
> with that name. Make sure that the name is entered correctly.
> any ideas?
>
|||flag 3608 yes, it was enabled.
About the steps you mentioned, i followed Q224071 and it has the order like
these:
1. moving msdb
2. moving master
3. moving model
4. moving tempdb
Could you confirm where you got your order?
"oj" wrote:

> Did you enable trace flag 3608 and reattach model database before msdb?
> The proper steps are:
> 1. moving master
> 2. moving model
> 3. moving msdb
> 4. moving tempdb
>
> --
> -oj
>
> "Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
> message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
>
>
|||No attach wasnt successful. End up with error:
Could not locate entry in sysdatabases for database model. No entry found
with that name. Make sure that the name is entered correctly.
"Yogish" wrote:

> Hi,
> Was sp_attach_db statement successfull? And did you try to remove -T3608
> flag from the startup parameter?
> If you have done the above, try to re-start the server and see what the
> error log has to say.
> --
> Thanks
> Yogish
|||Make sure you attached them in the right order, I had a similar issue where
msdb became model (as well as msdb) because of a typo when attaching the
model database, led to some odd behaviour :-)
Life without model
http://www.sqlteam.com/item.asp?ItemID=10060
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
message news:59F5AFE2-A996-46BF-8E53-B4D19480836B@.microsoft.com...
> When moving the sysdatabases to a different drive using specific Q224071
> ()
> instructions i found that the model db does not show up and when running:
> use model
> go
> sp helpfile
> go
> i get:
> Could not locate entry in sysdatabases for database model. No entry found
> with that name. Make sure that the name is entered correctly.
> any ideas?
>
|||It's clearly stated that model must be attached before msdb in kb 224071.
The actually order for master/tempdb is not that important when you're
moving system databases.
Moving the MSDB database (SQL Server 2000)
Note If you are using this procedure in conjunction with moving the msdb and
model databases, the order of reattachment must be model first and then
msdb. If msdb is reattached first, it must be detached and not reattached
until after model has been attached.
-oj
"Christian Castro" <ChristianCastro@.discussions.microsoft.com> wrote in
message news:C3F4F8D7-135E-4113-9423-92566B6BE454@.microsoft.com...[vbcol=seagreen]
> flag 3608 yes, it was enabled.
> About the steps you mentioned, i followed Q224071 and it has the order
> like
> these:
> 1. moving msdb
> 2. moving master
> 3. moving model
> 4. moving tempdb
> Could you confirm where you got your order?
> "oj" wrote:

Model and File Paths

I thought that the file path of the model is what would be used, when
creating a new database. I moved the logfile to it's own drive, and it all
works fine. However, when I create a new DB, it still shows that the Log
file goes to the same directory as my data file.
Am I missing something?
Can someone help me set my system, so newly created DB's are DEFAULT to:
d:\mssql\data = mdf files
e:\mssql\logs = ldf files
Thanks.
Kevin
I bet you created the database via EM. Take a look at CREATE DATABASE topic
in the BOL
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:ezw0GVNIGHA.1836@.TK2MSFTNGP11.phx.gbl...
>I thought that the file path of the model is what would be used, when
>creating a new database. I moved the logfile to it's own drive, and it all
>works fine. However, when I create a new DB, it still shows that the Log
>file goes to the same directory as my data file.
> Am I missing something?
> Can someone help me set my system, so newly created DB's are DEFAULT to:
> d:\mssql\data = mdf files
> e:\mssql\logs = ldf files
> Thanks.
>
|||Hi Kevin
this can be set up in two places - one during the installation - which
you could go back to using the REBUILDM.EXE utility I think - or right
click at the server level for you SQL Server in Enterprise manager and
you can set it on a tab under there - you may have to restart SQL
Server to force it in.
Model DB is the basis on all future DB creations - ie if you need to
set Collation on a particular column for future databases, you can set
it here and it will apply on all new databases. Also, you can set the
sizes on Model, so all future databases will have that property (ie
Immediate 50Mb MDF file)
Cheers
Steve L
|||That was it Steve, thanks! <right click> on EM and set it there. I queried
BOL but couldn't find anything about that setting.
Thanks again!
"Steve L" <steve_lawrenson@.tiscali.co.uk> wrote in message
news:1138104852.069486.319350@.g44g2000cwa.googlegr oups.com...
> Hi Kevin
> this can be set up in two places - one during the installation - which
> you could go back to using the REBUILDM.EXE utility I think - or right
> click at the server level for you SQL Server in Enterprise manager and
> you can set it on a tab under there - you may have to restart SQL
> Server to force it in.
> Model DB is the basis on all future DB creations - ie if you need to
> set Collation on a particular column for future databases, you can set
> it here and it will apply on all new databases. Also, you can set the
> sizes on Model, so all future databases will have that property (ie
> Immediate 50Mb MDF file)
> Cheers
> Steve L
>

Model and File Paths

I thought that the file path of the model is what would be used, when
creating a new database. I moved the logfile to it's own drive, and it all
works fine. However, when I create a new DB, it still shows that the Log
file goes to the same directory as my data file.
Am I missing something?
Can someone help me set my system, so newly created DB's are DEFAULT to:
d:\mssql\data = mdf files
e:\mssql\logs = ldf files
Thanks.Kevin
I bet you created the database via EM. Take a look at CREATE DATABASE topic
in the BOL
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:ezw0GVNIGHA.1836@.TK2MSFTNGP11.phx.gbl...
>I thought that the file path of the model is what would be used, when
>creating a new database. I moved the logfile to it's own drive, and it all
>works fine. However, when I create a new DB, it still shows that the Log
>file goes to the same directory as my data file.
> Am I missing something?
> Can someone help me set my system, so newly created DB's are DEFAULT to:
> d:\mssql\data = mdf files
> e:\mssql\logs = ldf files
> Thanks.
>|||Hi Kevin
this can be set up in two places - one during the installation - which
you could go back to using the REBUILDM.EXE utility I think - or right
click at the server level for you SQL Server in Enterprise manager and
you can set it on a tab under there - you may have to restart SQL
Server to force it in.
Model DB is the basis on all future DB creations - ie if you need to
set Collation on a particular column for future databases, you can set
it here and it will apply on all new databases. Also, you can set the
sizes on Model, so all future databases will have that property (ie
Immediate 50Mb MDF file)
Cheers
Steve L|||That was it Steve, thanks! <right click> on EM and set it there. I queried
BOL but couldn't find anything about that setting.
Thanks again!
"Steve L" <steve_lawrenson@.tiscali.co.uk> wrote in message
news:1138104852.069486.319350@.g44g2000cwa.googlegroups.com...
> Hi Kevin
> this can be set up in two places - one during the installation - which
> you could go back to using the REBUILDM.EXE utility I think - or right
> click at the server level for you SQL Server in Enterprise manager and
> you can set it on a tab under there - you may have to restart SQL
> Server to force it in.
> Model DB is the basis on all future DB creations - ie if you need to
> set Collation on a particular column for future databases, you can set
> it here and it will apply on all new databases. Also, you can set the
> sizes on Model, so all future databases will have that property (ie
> Immediate 50Mb MDF file)
> Cheers
> Steve L
>

Model and File Paths

I thought that the file path of the model is what would be used, when
creating a new database. I moved the logfile to it's own drive, and it all
works fine. However, when I create a new DB, it still shows that the Log
file goes to the same directory as my data file.
Am I missing something?
Can someone help me set my system, so newly created DB's are DEFAULT to:
d:\mssql\data = mdf files
e:\mssql\logs = ldf files
Thanks.Kevin
I bet you created the database via EM. Take a look at CREATE DATABASE topic
in the BOL
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:ezw0GVNIGHA.1836@.TK2MSFTNGP11.phx.gbl...
>I thought that the file path of the model is what would be used, when
>creating a new database. I moved the logfile to it's own drive, and it all
>works fine. However, when I create a new DB, it still shows that the Log
>file goes to the same directory as my data file.
> Am I missing something?
> Can someone help me set my system, so newly created DB's are DEFAULT to:
> d:\mssql\data = mdf files
> e:\mssql\logs = ldf files
> Thanks.
>|||Hi Kevin
this can be set up in two places - one during the installation - which
you could go back to using the REBUILDM.EXE utility I think - or right
click at the server level for you SQL Server in Enterprise manager and
you can set it on a tab under there - you may have to restart SQL
Server to force it in.
Model DB is the basis on all future DB creations - ie if you need to
set Collation on a particular column for future databases, you can set
it here and it will apply on all new databases. Also, you can set the
sizes on Model, so all future databases will have that property (ie
Immediate 50Mb MDF file)
Cheers
Steve L|||That was it Steve, thanks! <right click> on EM and set it there. I queried
BOL but couldn't find anything about that setting.
Thanks again!
"Steve L" <steve_lawrenson@.tiscali.co.uk> wrote in message
news:1138104852.069486.319350@.g44g2000cwa.googlegroups.com...
> Hi Kevin
> this can be set up in two places - one during the installation - which
> you could go back to using the REBUILDM.EXE utility I think - or right
> click at the server level for you SQL Server in Enterprise manager and
> you can set it on a tab under there - you may have to restart SQL
> Server to force it in.
> Model DB is the basis on all future DB creations - ie if you need to
> set Collation on a particular column for future databases, you can set
> it here and it will apply on all new databases. Also, you can set the
> sizes on Model, so all future databases will have that property (ie
> Immediate 50Mb MDF file)
> Cheers
> Steve L
>sql

MNS Quorum Drive

Hi,
Can we do this:
Configuration: A 3-node SQL server cluster that uses a
majority node set (MNS) quorum. The quorum would be an MNS
quorum where the quorum is stored locally on each node's
system disk. There is no shared storage. Each node has an
internal RAID-1 mirrored disk. So it looks like just one
disk local to the node.
We want to install Windows 2003 Enterprise, SQL Server
Enterprise, the database, and the MNS quorum drive on each
local disk. Is this a supported configuration? I was
reading that the database and quorum should be on
different disks but what about and when you have an MNS
quorum?
Thanks,
Todd
Majority Node Set is not supported for SQL Clustering.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:2263d01c45dde$33dcd590$a601280a@.phx.gbl...
> Hi,
> Can we do this:
> Configuration: A 3-node SQL server cluster that uses a
> majority node set (MNS) quorum. The quorum would be an MNS
> quorum where the quorum is stored locally on each node's
> system disk. There is no shared storage. Each node has an
> internal RAID-1 mirrored disk. So it looks like just one
> disk local to the node.
> We want to install Windows 2003 Enterprise, SQL Server
> Enterprise, the database, and the MNS quorum drive on each
> local disk. Is this a supported configuration? I was
> reading that the database and quorum should be on
> different disks but what about and when you have an MNS
> quorum?
> Thanks,
> Todd
|||Majority Node Set is not supported for SQL Clustering.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:2263d01c45dde$33dcd590$a601280a@.phx.gbl...
> Hi,
> Can we do this:
> Configuration: A 3-node SQL server cluster that uses a
> majority node set (MNS) quorum. The quorum would be an MNS
> quorum where the quorum is stored locally on each node's
> system disk. There is no shared storage. Each node has an
> internal RAID-1 mirrored disk. So it looks like just one
> disk local to the node.
> We want to install Windows 2003 Enterprise, SQL Server
> Enterprise, the database, and the MNS quorum drive on each
> local disk. Is this a supported configuration? I was
> reading that the database and quorum should be on
> different disks but what about and when you have an MNS
> quorum?
> Thanks,
> Todd