Connecting to SQLServer 2000 using DNS alias

Hi all,

I have to move my SQlServer 2000 instance from one server
'actual_server' to another server 'new_server'.
But, the different applications connecting to the actual server can't
easily change their connections address. i.e it connect to
'actual_server' server only.

Is there a risk to declare a DNS alias 'actual_server' pointing to
'new_server' ?
So I could move my databases from 'actual_server' to 'new_server'.
Is the modification transparent to the client ?
I especially thinking about wins...

TYIA
Cordially
RJP"rjp" <rjp.l@.laposte.net> wrote in message
news:9b7a7215.0410130818.317ad44b@.posting.google.c om...
> Hi all,
> I have to move my SQlServer 2000 instance from one server
> 'actual_server' to another server 'new_server'.
> But, the different applications connecting to the actual server can't
> easily change their connections address. i.e it connect to
> 'actual_server' server only.
> Is there a risk to declare a DNS alias 'actual_server' pointing to
> 'new_server' ?
> So I could move my databases from 'actual_server' to 'new_server'.
> Is the modification transparent to the client ?
> I especially thinking about wins...
> TYIA
> Cordially
> RJP

I don't see any big problem, if you're simply adding an alias to an existing
host. It probably isn't a good long-term solution, though, as it may create
management and troubleshooting problems at some point. I don't know about
WINS, as I haven't used it in a while (it's not necessary on an all-Win2K
TCP/IP network) - you might want to check with your network administrators
(if that's not you, of course), or in a networking newsgroup.

Simon|||> I don't see any big problem, if you're simply adding an alias to an
existing
> host. It probably isn't a good long-term solution, though, as it may
create
> management and troubleshooting problems at some point. I don't know about
> WINS, as I haven't used it in a while (it's not necessary on an all-Win2K
> TCP/IP network) - you might want to check with your network administrators
> (if that's not you, of course), or in a networking newsgroup.
> Simon

Thanks Simon.
:)

Connecting to SQL2000 using DNS Alias/Named Pipes

Hi,
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas?
Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpmsftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.

Connecting to SQL2000 using DNS Alias/Named Pipes

Hi,
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas'Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpmsftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.

Connecting to SQL2000 using DNS Alias/Named Pipes

Hi,
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas'Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpm
sftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes
.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS th
e
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.

Connecting to SQL Server with an alias

We have a soon-to-be legacy Sql Server called X. We have several queries on
various other servers configured to talk to X thru a linked server that go
something like:
SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
X will now be hosted on a new machine called Y.
So my question is, is there a way of aliasing our new server called "Y" so
that it can be refered to as "X"?
TIA//
I believe that you can do this using sp_addlinkedserver. Check out Books Online
(sp_addlinkedserver), the second example in the table. This suggests that you can specify some other
name for the linked server than the network name.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Newby" <Chris.Newby@.Rockcreekglobal.com> wrote in message
news:%23LXjZH6FGHA.1676@.TK2MSFTNGP09.phx.gbl...
> We have a soon-to-be legacy Sql Server called X. We have several queries on various other servers
> configured to talk to X thru a linked server that go something like:
> SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
> X will now be hosted on a new machine called Y.
> So my question is, is there a way of aliasing our new server called "Y" so that it can be refered
> to as "X"?
> TIA//
>
|||So you are using a linked server to achive the connection to the server
X. Defining a server alias within the network client tool should do the
trick.
HTH, jens Suessmeyer.

Connecting to SQL Server with an alias

We have a soon-to-be legacy Sql Server called X. We have several queries on
various other servers configured to talk to X thru a linked server that go
something like:
SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
X will now be hosted on a new machine called Y.
So my question is, is there a way of aliasing our new server called "Y" so
that it can be refered to as "X"?
TIA//I believe that you can do this using sp_addlinkedserver. Check out Books Online
(sp_addlinkedserver), the second example in the table. This suggests that you can specify some other
name for the linked server than the network name.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Newby" <Chris.Newby@.Rockcreekglobal.com> wrote in message
news:%23LXjZH6FGHA.1676@.TK2MSFTNGP09.phx.gbl...
> We have a soon-to-be legacy Sql Server called X. We have several queries on various other servers
> configured to talk to X thru a linked server that go something like:
> SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
> X will now be hosted on a new machine called Y.
> So my question is, is there a way of aliasing our new server called "Y" so that it can be refered
> to as "X"?
> TIA//
>|||So you are using a linked server to achive the connection to the server
X. Defining a server alias within the network client tool should do the
trick.
HTH, jens Suessmeyer.

Connecting to SQL Server with an alias

We have a soon-to-be legacy Sql Server called X. We have several queries on
various other servers configured to talk to X thru a linked server that go
something like:
SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
X will now be hosted on a new machine called Y.
So my question is, is there a way of aliasing our new server called "Y" so
that it can be refered to as "X"?
TIA//I believe that you can do this using sp_addlinkedserver. Check out Books Onl
ine
(sp_addlinkedserver), the second example in the table. This suggests that yo
u can specify some other
name for the linked server than the network name.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Newby" <Chris.Newby@.Rockcreekglobal.com> wrote in message
news:%23LXjZH6FGHA.1676@.TK2MSFTNGP09.phx.gbl...
> We have a soon-to-be legacy Sql Server called X. We have several queries o
n various other servers
> configured to talk to X thru a linked server that go something like:
> SELECT [columnName] FROM [X].[DBName].[dbo].[TableName
]
> X will now be hosted on a new machine called Y.
> So my question is, is there a way of aliasing our new server called "Y" so
that it can be refered
> to as "X"?
> TIA//
>|||So you are using a linked server to achive the connection to the server
X. Defining a server alias within the network client tool should do the
trick.
HTH, jens Suessmeyer.

Connecting to SQL Server 2005 on local machine via an alias in the hosts file

Don't know if it works for .NET but creating an Alias could be the solution
to your problem. See SQL Server Configuration Manager | SQL Native Client
Configuration | Alias. Using an alias is usually much better than fiddling
with the Host file but as I said, I never tried them with .NET.
Finally, from your connection string, I'm not sure if you are using the
Native Provider for SQL-Server 2005 instead of the older provider for
SQL-Server 2000. Maybe your problem with 127.0.0.1 comes from that. I also
don't understand why you are using the connection reset=false parameter.
This parameter should only be used when you are not using the connection
pooling.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Sam" <samchurchill82@.gmail.com> wrote in message
news:45ea7082-6c27-4f12-85a8-0c33aec870d7@.b15g2000hsa.googlegroups.com...
> Hi,
> I work in a team of .NET developers who all have a local version of
> SQL Server 2005 on their PC for normal development projects. However,
> sometimes more than one of us has to work on the same server for
> development as we are sharing data. If we change the server name in
> the connection string in our application's config file from "(local)"
> to "SharedDevelopmentServer" and check it in to source control all of
> the other developers will get it and suddenly be using the shared
> server rather that their own local server. We got into the situation
> where the config file was being checked in and out every 15 minutes
> because one group wanted it to be "(local)" and the other group wanted
> it to be "SharedDevelopmentServer".
> I thought I had an elegant solution to this: make the server in the
> config file's connection string point to a non-existant server called
> "DevelopmentServer", then each developer could add a record into his
> HOSTS file to point this DNS alias to the IP address of the server
> that they want to use at that time. This works very well if the
> development server that you want to point to is not localhost but for
> some reason it gives the following error if you try to use your own IP
> address (or the loopback 127.0.0.1 address).
> Login failed for user ''. The user is not associated with a trusted
> SQL Server connection.
> It looks as if it's not passing through my credentials properly so
> it's not able to authenticate me. Our connection string is as
> follows:
> <add name="MyConnectionString" connectionString="data
> source=DevelopmentServer;database=MyDatabase;Integ rated
> Security=SSPI;application name=MyApplication;Connection Reset=false"
> providerName="System.Data.SqlClient" />
> Has anyone got any ideas how to resolve this or use another way of
> mapping to our selected development server which could be different
> for everyone in the team?
> Many thanks,
> Sam
"Sam" <samchurchill82@.gmail.com> wrote in message
news:595337f6-a7ae-4161-aad2-10d871991aac@.q77g2000hsh.googlegroups.com...
> On 11 Dec, 17:18, "Sylvain Lafontaine" <sylvain aei ca (fill the
> blanks, no spam please)> wrote:
> Thanks, that works a treat. I guess any application trying to connect
> to an SQL server on my machine must be going via this before it hits
> DNS.
To my knowledge, aliases are only for the client side; the server never sees
them; so the answer would be yes: any application willing to use an alias
must set it up on its side. Notice that you can also use a TCP/IP address
(like 127.0.0.1) as an alias; so they are definitely looked up before the
DNS servers.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)