Re: Fix of problem connecting VS2005 to remote Sql 2000 server
- From: "RvGrah" <rvgrahamsevatenein@xxxxxxxxxxxxx>
- Date: 6 Mar 2006 14:04:25 -0800
How should you connect to a remote Sql server across a vpn connection
if you shouldn't use the "np:" named pipes prefixing? (I am in a
working across corporate networks, although we're talking about quite
diminutive corporations.)
Or when I'm in Sql Management Studio and wish to push some database
tables to our branch office (not really a branch, more of a clone
company in another state that shares the same software development and
database design). In Sql Server 2000 Enterprise Manager, if I just made
a vpn connection to the remote office, I could copy tables or stored
procedures etc from server to server without any special effort. Is
using np:<servername> not the right way to do it using 2005 tools? I
want to use the newer interface to get accustomed to it, and because it
offers superior tools for copying tables, as a for instance.
Any further guidance appreciated.
Bob
.
- Follow-Ups:
- Re: Fix of problem connecting VS2005 to remote Sql 2000 server
- From: Willy Denoyette [MVP]
- Re: Fix of problem connecting VS2005 to remote Sql 2000 server
- References:
- Fix of problem connecting VS2005 to remote Sql 2000 server
- From: RvGrah
- Re: Fix of problem connecting VS2005 to remote Sql 2000 server
- From: Willy Denoyette [MVP]
- Re: Fix of problem connecting VS2005 to remote Sql 2000 server
- From: Willy Denoyette [MVP]
- Fix of problem connecting VS2005 to remote Sql 2000 server
- Prev by Date: Re: Static Indexer - Why Not?
- Next by Date: Re: Attributes (net1.1) Quick answer needed
- Previous by thread: Re: Fix of problem connecting VS2005 to remote Sql 2000 server
- Next by thread: Re: Fix of problem connecting VS2005 to remote Sql 2000 server
- Index(es):
Relevant Pages
|
Loading