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:

Missing dll folder in SQL Server 2005

Hello, I have have some instructions to put a dll file in the folder
"C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
do you think I would be the dll.
ThanksHi Don,
Are these instructions from a specific application? Does it mention if it is
compatible with SQL Server 2005?
Ben Nevarez
"Don" wrote:
> Hello, I have have some instructions to put a dll file in the folder
> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
> machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
> folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
> do you think I would be the dll.
> Thanks
>|||Exactly my thoughts, Ben. My guess is that it is an extended stored procedure, and if the
instructions doesn't say how to install it on 2005, we shouldn't assume it has been tested on 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:D1FD01B8-51AC-4570-92C7-EB0254257714@.microsoft.com...
> Hi Don,
> Are these instructions from a specific application? Does it mention if it is
> compatible with SQL Server 2005?
> Ben Nevarez
>
>
> "Don" wrote:
>> Hello, I have have some instructions to put a dll file in the folder
>> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
>> machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
>> folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
>> do you think I would be the dll.
>> Thanks|||Yes, it's for a extended stored procedure called xp_calendar. And there are
notes about having it work with SQl 2005 just not about were to put the dll.
I had installed it on a SQL Server 2000 as a test and xp_calendar worked
well, but when I went to install it at the client running 2005 I saw that it
does not have the dll folder.
http://www.sqlservercentral.com/articles/Miscellaneous/2985/
http://www.logicom-inc.com/xp_sql2exchange/xp_sql2exchange.html
Thanks
Don
"Tibor Karaszi" wrote:
> Exactly my thoughts, Ben. My guess is that it is an extended stored procedure, and if the
> instructions doesn't say how to install it on 2005, we shouldn't assume it has been tested on 2005.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:D1FD01B8-51AC-4570-92C7-EB0254257714@.microsoft.com...
> >
> > Hi Don,
> >
> > Are these instructions from a specific application? Does it mention if it is
> > compatible with SQL Server 2005?
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "Don" wrote:
> >
> >> Hello, I have have some instructions to put a dll file in the folder
> >> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
> >> machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
> >> folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
> >> do you think I would be the dll.
> >>
> >> Thanks
> >>
>
>|||I would add the files to the binn folder and then adjust the paths in the file "xp_add.sql"
accordingly. You would need to find what folder (MSSQL.1 etc) corresponds to your instance name,
check the below reg key for that:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Don" <Don@.discussions.microsoft.com> wrote in message
news:0AC640AC-92C5-478F-82EA-6DD80D9BB418@.microsoft.com...
> Yes, it's for a extended stored procedure called xp_calendar. And there are
> notes about having it work with SQl 2005 just not about were to put the dll.
> I had installed it on a SQL Server 2000 as a test and xp_calendar worked
> well, but when I went to install it at the client running 2005 I saw that it
> does not have the dll folder.
> http://www.sqlservercentral.com/articles/Miscellaneous/2985/
> http://www.logicom-inc.com/xp_sql2exchange/xp_sql2exchange.html
> Thanks
> Don
> "Tibor Karaszi" wrote:
>> Exactly my thoughts, Ben. My guess is that it is an extended stored procedure, and if the
>> instructions doesn't say how to install it on 2005, we shouldn't assume it has been tested on
>> 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:D1FD01B8-51AC-4570-92C7-EB0254257714@.microsoft.com...
>> >
>> > Hi Don,
>> >
>> > Are these instructions from a specific application? Does it mention if it is
>> > compatible with SQL Server 2005?
>> >
>> > Ben Nevarez
>> >
>> >
>> >
>> >
>> > "Don" wrote:
>> >
>> >> Hello, I have have some instructions to put a dll file in the folder
>> >> "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\dll" which I see on a
>> >> machine with SQL Server 2000. On machines with SQL Server 2005 you have 3
>> >> folders MSSQL.1, MSSQL.2, MSSQL.3 and none of them have a dll folder. Where
>> >> do you think I would be the dll.
>> >>
>> >> Thanks
>> >>
>>