Posted by Akinja on 07/02/05 01:00

That sounds logical. However, this seems a little strange that I would list
two different locations within various system tables. I am hoping this is
not a receipt for a problem later on. Make you want to say 'Uhmmm'

What I meant by moving the system databases was that on the new servers, D:\
was too small for all the databases. So I needed to place the system dbs
there and bring up the server. The databases will come up Suspect. In
order to move Master, I needed to change the startup parameters to reflect
the new location. In order to change model and msdb (in that order) I
needed to add a trace flag 3608 to the startup parameters then detach, move,
and reattach the database. Temp just required an Alter statement.

Appreciate the feedback (a real puzzle)

Akinja

"Ross Presser" <rpresser@NOSPAMgmail.com.invalid> wrote in message
news:3l4hl7rz52w1.1x6k3djsmrfra$.dlg@40tude.net...
> On Fri, 01 Jul 2005 18:40:28 GMT, Akinja wrote:
>
>> Any ideas why the two are not showing the same thing? Everything is
>> working
>> fine and all other databases (sp_helpdb) is correct and sp_helpfile
>> master
>> is showing the same thing as sp_helpdb master. Since I though sp_helpdb
>> was
>> querying sysdatabases, I am confused as to why this is happening.
>>
>> Any help would be greatly appreciated. Sorry for the long post.
>
> Using Query analyzer, I scripted master.dbo.sp_helpdb to inspect it. In
> fact it queries sysdatabases for the first resultset - the one that lists
> name,db_size,owner,dbid,created,status,compatibility_level . But for the
> second resultset, that shows the file allocation, it is in fact invoking
> sp_helpfile. So the filename column in sysdatabases isn't referenced by
> sp_helpdb at all.
>
> sp_helpfile doesn't look at sysdatabases at all, it looks at sysfiles.
>
> I am guessing that what you describe as
>> some work that you must do to move the master, msdb, model, and temp to
>> the new location (change the startup parameters and detaching and
>> reattaching some other databases)
> does not in fact change the column in sysdatabases, and that that column
> is
> not really used in system startup.

[Back to original message]