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
>
Showing posts with label moved. Show all posts
Showing posts with label moved. Show all posts
Monday, March 26, 2012
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
>
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
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
Monday, March 12, 2012
Missing system stored procedures
I developed a Pocket PC app that uses merge replication in an isolated
development environment. It worked fine. The I moved to the operational
environment. Synchronization fails with error 2812, "Could not find stored
procedure 'sp_MSgetmakegenerationapplock'". A little investigation shows that
in the development environment, that stored procedure exists, but it does not
exist on the operational SQL Server. (The total sp count on the development
server is 969, on the operational server 930, so other sp's are also
missing). I disabled replication on the operational server and then
reconfigured it, but that didn't help.
The operational SQL Server is SQL Server 2000 Standard Edition running sp3a.
Any ideas why those sp's didn't get created, and how to fix this problem?
There's a message thread out there that suggests that xp_cmdshell is needed
to properly create some replication-related sp's. Is it possible that
xp_cmdshell is missing or disabled? However, when I configure the server for
replication, I don't get any error messages.
You need to reapply the sp. This problem has been observed before.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"PGallez" <PGallez@.discussions.microsoft.com> wrote in message
news:8A112E32-D0BB-4FB5-9A51-B62BBAFBAB01@.microsoft.com...
> I developed a Pocket PC app that uses merge replication in an isolated
> development environment. It worked fine. The I moved to the operational
> environment. Synchronization fails with error 2812, "Could not find stored
> procedure 'sp_MSgetmakegenerationapplock'". A little investigation shows
that
> in the development environment, that stored procedure exists, but it does
not
> exist on the operational SQL Server. (The total sp count on the
development
> server is 969, on the operational server 930, so other sp's are also
> missing). I disabled replication on the operational server and then
> reconfigured it, but that didn't help.
> The operational SQL Server is SQL Server 2000 Standard Edition running
sp3a.
> Any ideas why those sp's didn't get created, and how to fix this problem?
> There's a message thread out there that suggests that xp_cmdshell is
needed
> to properly create some replication-related sp's. Is it possible that
> xp_cmdshell is missing or disabled? However, when I configure the server
for
> replication, I don't get any error messages.
|||Thanks much, I'll give that a try.
"Hilary Cotter" wrote:
> You need to reapply the sp. This problem has been observed before.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "PGallez" <PGallez@.discussions.microsoft.com> wrote in message
> news:8A112E32-D0BB-4FB5-9A51-B62BBAFBAB01@.microsoft.com...
> that
> not
> development
> sp3a.
> needed
> for
>
>
development environment. It worked fine. The I moved to the operational
environment. Synchronization fails with error 2812, "Could not find stored
procedure 'sp_MSgetmakegenerationapplock'". A little investigation shows that
in the development environment, that stored procedure exists, but it does not
exist on the operational SQL Server. (The total sp count on the development
server is 969, on the operational server 930, so other sp's are also
missing). I disabled replication on the operational server and then
reconfigured it, but that didn't help.
The operational SQL Server is SQL Server 2000 Standard Edition running sp3a.
Any ideas why those sp's didn't get created, and how to fix this problem?
There's a message thread out there that suggests that xp_cmdshell is needed
to properly create some replication-related sp's. Is it possible that
xp_cmdshell is missing or disabled? However, when I configure the server for
replication, I don't get any error messages.
You need to reapply the sp. This problem has been observed before.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"PGallez" <PGallez@.discussions.microsoft.com> wrote in message
news:8A112E32-D0BB-4FB5-9A51-B62BBAFBAB01@.microsoft.com...
> I developed a Pocket PC app that uses merge replication in an isolated
> development environment. It worked fine. The I moved to the operational
> environment. Synchronization fails with error 2812, "Could not find stored
> procedure 'sp_MSgetmakegenerationapplock'". A little investigation shows
that
> in the development environment, that stored procedure exists, but it does
not
> exist on the operational SQL Server. (The total sp count on the
development
> server is 969, on the operational server 930, so other sp's are also
> missing). I disabled replication on the operational server and then
> reconfigured it, but that didn't help.
> The operational SQL Server is SQL Server 2000 Standard Edition running
sp3a.
> Any ideas why those sp's didn't get created, and how to fix this problem?
> There's a message thread out there that suggests that xp_cmdshell is
needed
> to properly create some replication-related sp's. Is it possible that
> xp_cmdshell is missing or disabled? However, when I configure the server
for
> replication, I don't get any error messages.
|||Thanks much, I'll give that a try.
"Hilary Cotter" wrote:
> You need to reapply the sp. This problem has been observed before.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "PGallez" <PGallez@.discussions.microsoft.com> wrote in message
> news:8A112E32-D0BB-4FB5-9A51-B62BBAFBAB01@.microsoft.com...
> that
> not
> development
> sp3a.
> needed
> for
>
>
Subscribe to:
Posts (Atom)