RE: How to connect test to production system

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

changliw@xxxxxxxxxxxxxxxxxxxx (Charles Wang[MSFT]) wrote in
news:M55syrX3HHA.4100@xxxxxxxxxxxxxxxxxxxxxx:

Hi David,

[snip]

You may try adding some server aliases on your test systems. These
server aliases have the same names as the server names in production.
For example, your test SQL Server instance name is "Server1\SQL2K",
while your production SQL Server instance name is
"ProductServer\SQLServer". You can first run cliconfg.exe (SQL 2000
client) from command line or SQL Server Configuration Manager (SQL
2005 client) on your client computer to configure a server alias
"ProductServer\SQLServer" which represents your test SQL Server
instance "Server1\SQL2K" with a specific protocol (TCP/IP or Named
Pipes). After that, you can run:
Sp_addlinkedserver 'ProductServer\SQLSERVER'
Go
Sp_addlinkedsrvlogin 'ProductServer\SQLSERVER','True'
Go
Then you can run the following statement to query the northwind
database in your local test SQL Server instance "Server1\SQL2K":
SELECT * FROM [ProductServer\SQLServer].northwind.dbo.employees


Charles,

If I use the sp_addlinkedserver and sp_addlinkedsrvlogin, then I *don't*
need to use cliconfig first. Adding the linked server does the whole
thing. I got it to work this way.

Thanks.

David
.

Relevant Pages

  • RE: Error installing (KB 921896)
    ... instance MSSMLBIZ ... to SQL Server. ... correct or check to see if the SQL Server Instance is set to Mixed ... the SQL Server Instance is set to Mixed Authentication ...
    (microsoft.public.windowsupdate)
  • Re: SQL 200 Dev edition on workgroup will not connect
    ... I have been using sql server for about 8 years but mainly working with sql 2000. ... know your experience level with SQL Server and yes, sometimes things being messy but letting a SQL Server instance to accept remote connections and uninstalling it are generally straightforward tasks to perform. ... I suggest you to check for the dynamic port number that your SQL Server graps. ... Write down the port number in the "TCP Dynamic Ports" property and then run a Command Prompt and see if this port is bening listened. ...
    (microsoft.public.sqlserver.connect)
  • Re: Installing Sql Server Express on Vista Home Premium
    ... What comes to my mind is that there is a Default SQL Server instance is installed on that working system and your application connects to that instance. ... This connection string should work as you do not force the connection to use a specific protocol, Shared Memory will be used as this is the primary protocol by default. ... Default Instances uses 1433 TCP port by default as a Static Port but not the ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL 200 Dev edition on workgroup will not connect
    ... Will you show me the Connection String you use for your application to connect to your remote SQL Server instance? ... I suggest you to check for the dynamic port number that your SQL Server graps. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Server 2005 and security patch issues?
    ... I guess the problem occurs while you are trying to log in to your SQL Server instance, if so, do you get any error message? ... I recreated a fresh instance and a fresh copy of the ...
    (microsoft.public.sqlserver.security)