RE: How to connect test to production system
- From: changliw@xxxxxxxxxxxxxxxxxxxx (Charles Wang[MSFT])
- Date: Mon, 13 Aug 2007 07:24:00 GMT
Hi David,
Since your post has a good many of information, I would like to first
confirm with you if I understand your environment:
1. Your main computer connected to your home office network via VPN;
2. Your local SQL Server computer connected to your main computer via
Ethernet (Local Area Network); It did not directly connect to your home
office network;
3. Your local SQL Server could connect to a remote SQL Server in your home
office network with a specific destination TCP port opened.
Also, I have two questions and appreciate your confirmation since I have
not totally understood your scenario:
1. What is the relationship between your main computer and your local SQL
Server computer?
2. Which computer is your local copy of the main database located on, the
main computer or the local SQL Server computer?
For your two questions,
1) Given that I now have a VPN, and the "main" computer is multihomed,
should I be able to link the database on my local SQL server to the
databases at the home office?
Did you mean databases in different server instances here? If the databases
at the home office were all in the remote SQL Server with specific TCP port
opened, your local SQL Server should be able to connect to the databases in
the remote SQL Server instance.
If you meant that you would like to access the databases in different SQL
Server instances (may be located on different servers) at your home office
via linked server via your local SQL Server, you may try adding your main
server as the gateway of your local SQL Server computer to see if it helps.
Anyway, you need to ensure that the physical connections from your local
SQL Server computer to your remote servers could be established.
If the physical network connections could be established, you can add the
linked servers with SQL authentication (if Windows Authentication could not
be established).
2) How do people develop views and stored procs on test systems, when the
call-out to the linked server might need a different server name in
production?
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
For configure server alias on a client computer, you may also refer to:
How to connect to a named instance of SQL Server 2005 or SQL Server 2000 by
using the client tools in the earlier version of SQL Server
http://support.microsoft.com/kb/265808/en-us
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- Follow-Ups:
- RE: How to connect test to production system
- From: DWalker
- RE: How to connect test to production system
- From: DWalker
- RE: How to connect test to production system
- References:
- How to connect test to production system
- From: DWalker
- How to connect test to production system
- Prev by Date: Re: Shared Memory from older app SQL Server 2005
- Next by Date: Re: Unable to connect to SQL 2000 engine on other machine from SSM
- Previous by thread: Re: How to connect test to production system
- Next by thread: RE: How to connect test to production system
- Index(es):
Relevant Pages
|
