> I'd go with a table. If that isn't an option, consider using extended
> properties, set on one of your tables.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
> "Graham R Seach" <gseach@NOSPAMpacificdb.com.au> wrote in message
> news:BF4380FD-BF05-4D5A-9887-9758CB6EC9D2@microsoft.com...
>> Hi guys,
>>
>> I am developing an application that front-ends to SQL Server 2000
>> Enterprise. I am trying to find a way of setting a custom database
>> property,
>> to let my application know whether the application is currently connected
>> to
>> the development db, or the production db.
>>
>> Neither the application or the physical servers have been installed yet,
>> and
>> I have no idea what the network admins are going to call the new servers
>> when
>> it does go live. I have no say in it.
>>
>> I have provided the facility for users to connect to a server/database,
>> from
>> a list, by the click of a button.
>>
>> I would rather not use a table for this, so the only other alternative I
>> can
>> think of is to set a database property. The problem is that I don't know
>> of
>> any properties I could use, or indeed how to use them if they are
>> available.
>>
>> Could someone shed some light on this for me?
>>
>> Regards,
>> Graham R Seach
>>
>
>

"Graham R Seach" <gseach@NOSPAMpacificdb.com.au> wrote in message
news:BF4380FD-BF05-4D5A-9887-9758CB6EC9D2@microsoft.com...
> Hi guys,
>
> I am developing an application that front-ends to SQL Server 2000
> Enterprise. I am trying to find a way of setting a custom database property,
> to let my application know whether the application is currently connected to
> the development db, or the production db.
>
> Neither the application or the physical servers have been installed yet, and
> I have no idea what the network admins are going to call the new servers when
> it does go live. I have no say in it.
>
> I have provided the facility for users to connect to a server/database, from
> a list, by the click of a button.
>
> I would rather not use a table for this, so the only other alternative I can
> think of is to set a database property. The problem is that I don't know of
> any properties I could use, or indeed how to use them if they are available.
>
> Could someone shed some light on this for me?
>
> Regards,
> Graham R Seach
>