>-----Original Message-----
>Can you not achieve the same thing using Cliconfg ?
>In here you create an Alias to whatever server you want=20
and call it whatever
>you want. You can then use the "Friendly name" from=20
there.
>
>"Cliconfg.exe is part of Microsoft Data Access Component=20
(MDAC). If
>Cliconfg.exe is not installed on your computer, you can=20
install it by
>running Sqlredis.exe from the SQL Server 2000=20
installation files.
>Sqlredis.exe is in the \x86\Other folder on the SQL=20
Server 2000 CD. For
>additional information about SQL Server 2000 Setup,=20
click the following
>article number257716 to view the article257716 in the=20
Microsoft Knowledge
>Base"
>
>--=20
>
>----------------------------
>Allan Mitchell (Microsoft SQL Server MVP)
>MCSE,MCDBA
>www.SQLDTS.com
>I support PASS - the definitive, global community
>for SQL Server professionals - http://www.sqlpass.org
>
>
>
>"G=E9 Brander" <anonymous@discussions.microsoft.com> wrote=20
in message
>news:016901c392dd$8b991900$a001280a@phx.gbl...
>> Hi,
>>
>> No we are using connection strings like
>> MACHINE_NAME\INSTANCE_NAME. This is not very flexible
>> when we need to move the databases from one
>> machine/instance to another machine/instance.
>>
>> What I would like is as follow:
>> Create a DNS entry for example: PRODAPP1 - name voor
>> Production environment for Application 1
>> Pointing to Machine 1 instance 1 on port 4001
>>
>> When we need to move a database to another Machine we
>> only need to change the DNS entry to point to for=20
example
>> Machine 3 instance 2 on port 6002.
>>
>> How do I configure this on the client side?
>> Can I put PRODAPP1 in the connection string and will
>> everything go fine? Or am I missing something that will
>> make this impossible?
>>
>> I will not be making use of any other protocol than
>> TCP/IP.
>>
>> Thanks in advance!
>>
>
>
>.