Re: inconsistent database naming scheme?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Dan Guzman (danguzman_at_nospam-earthlink.net)
Date: 07/16/04 

Date: Thu, 15 Jul 2004 19:38:53 -0500

> How could this happen?

Physical database file names can be any legal file name supported by your
file system:

CREATE DATABASE MyDatabase
ON(NAME='MyDatabase', FILENAME='C:\ICanNameThisAnything.abcde')
LOG ON(NAME='MyDatabase_Log', FILENAME='C:\ICanNameThisAnythingToo.defgh')

Andrew noted the suggested suffixes and it's a good practice to specify the
database name as the first part of the file name. The remainder of the file
name is up to you. Personally, I add a number to make the file name unique
and also include the filegroup name for files in user-defined filegroups. 

-- 
Hope this helps.
Dan Guzman
SQL Server MVP
"bing" <bing@discussions.microsoft.com> wrote in message
news:17493040-675C-432A-8D95-F845EDB7A4C1@microsoft.com...
> In my physical database directory, I found the databases were named in
several different ways:
>
> 1. db1.mdf
>     db1.ldf
>
> 2. db2_Data.MDF
>     db2_Log.LDF
>
> 3. db3.mdf
>     db3_Log.LDF
>
> 4. msdbdata.mdf
>     msdblog.ldf
>
> 5. model.mdf
>     modellog.ldf
>
> How could this happen?  I read the online books and just found that .mdf
and .ldf are generally standard suffix for database names.  What about other
parts of a name?  I do not remember how the names of these databases
originally looked like.  We're experiencing database corruptions these days.
Those database names just started looking suspicious to me.
>
> I would greatly appreciate any insights or pointers.
>
>
> Bing
Quantcast