Excellent point. You are right, the name of the database is used only in the connection string and this could be easily changed. Thank you.

>As a developer, I don't think you need to dwell on what to name the database at all. IMHO, it's up to the company where your software is being installed to name the database. Your software should be flexible enough to not hardcode database names in code (should all be done via config files).
>
>Just my opinion ...
>
>~~Bonnie
>
>
>
>>Hi,
>>
>>I was cruising through some articles on the web about database object naming conventions. I read one that stated the following about using names of databases:
>>

>>All database names must be prefixed with the originating component's acronym - e.g. CBC_Medicare Compare or 
>>EDG_Database_Tracking.  Use both upper and lower case as appropriate.
>>

>>
>>First I thought that the above requirement was silly (since I work for a small company - me <g>). But when I thought about moving a database to a customer site it started making sense. I don't know how many other databases they have and if I don't provide the prefix of department for which I do work, it could be confusing to DBA, right? So now I am thinking of prefixing my database (the only I am creating for the customer) with the acronym of the department. Does it make sense? Is this a typical convention of naming database with a prefix or the department?
>>
>>TIA