Arthur Fuller
artful at rogers.com
Wed Apr 16 14:03:40 CDT 2003
What's involved in your scenario? Purchase of a third-party VPN? Is there enough in win2k to do it? What's the performance hit for a VPN? In what way is client 1's SQL server wide open? Without a uid+pswd you can't get in. I sense that I'm missing something really basic here, but the only way to learn is to ask stupiid questions :-) A. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Djabarov, Robert Sent: April 16, 2003 2:52 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer]IP Connection to SQL As an alternative to both scenarios (having SQL wide open on 1's client and running TS on 2's client), I would recommend a VPN channel that you would connect to via your normal internet connection. After it's setup, make a shortcut and double-click...That's it! After that you can use your client 1's-like approach, - IP + UID + PWD. Doing so will eliminate the need for TS, and at the same time will not expose your client's databases like in client 1's case.