But, will I be able to connect to the source database from another network. I've done this from inside an intranet from one database to another, but never tried it from totally different network.
But, will I be able to connect to the source database from another network. I've done this from inside an intranet from one database to another, but never tried it from totally different network.
Are you talking about networks separated by a firewall or some other packet filtering? The answer would be 'maybe' - depends on what ports you have open. You'll need at least whatever port SQL Server is listening on open so that you can connect to it export from/import to the target. Default TCP/IP port is 1433. If you're using windows authentication, you might need the netbios ports open as well, which most admins won't open. You can use SQL Authentication, but then the password isn't encrypted.
I would strongly consider the use of VPN to tunnel into the target network, then initiate the connection, or setup a SQL 2k server inside the other network and detach/attach the database files to this new server then perform the import. Everything else has too many security holes in it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.