Connection Thru Internet

Hello again pals, i meet you again to ask an old question i had, but no found answer.

Can i connect to a remote SQL Server thru Internet, lets say from a client like Query Analyzer?

I read to make it using a VPN, but i try to configure it and cant get connected.

I'm using a Win2000 Server or Win2003 Server,

Thanksfull!!!!

There is many people asking for that, i start to think it cant be done! :'(If you are using virtual private networking (VPN) to get onto the network where the SQL Server resides, yes you can access a SQL Server throught the internet. You need a router that allows for VPN, there is some configuration to do here and depending on your SQL authentication method, you are going to either have to setup accounts for the users NT logins(windows authentication) or setup user names and passwords for these users. Do'nt forget to assign them permissions within SQL as well.|||If you are using virtual private networking (VPN)

There is no other way to do it, without using VPN?, it has been a headache to try configure it!

Thanks for your help Thrasymachus, is well received|||This is the only way I can think of if you want use the QA to access the data. You can always create an online interface to do what your users need but it sounds like they need a lot of access.|||If you know how to Telnet and use OSQL you can query your database from the command line|||If you make the ports that your server is listening on open to the internet you could connect directly. If you are using QA though I'd think you were doing some administrative tasks. You really shouldn't open up access to your server to the internet unless it's absolutely neccessary. If you can use a VPN, do it.|||Another way would be to set up port forwarding. But again it's as unsecure as directly exposing the server.

Connection problems

Am working on a SQL Server 2000 db with Powerbuilder 8 as the frontend. For
months our endusers connected thru the SQL Server native driver for version
6. Now, have just ported the application to Powerbuilder 10, and I
understand that the native drivers for SQL Server 2000 no longer exist in
Powerbuilder, and you are expected to use OLEDB or ODBC. Thinking that
OLEDB was the preferred method, I attempted to connect to the Server with
this Profile in Powerbuilder. I could connect fine, but it frooze everyone
else out. Anyone else have this problem, and if, how did you resolve it?
So, some more questions:
1). What is the preferred way to connect to SQL Server 2000, OLEDB or ODBC.
2). What is the fastest connection?William F. O'Neill (wfoneill@.bellsouth.net) writes:
> Am working on a SQL Server 2000 db with Powerbuilder 8 as the frontend.
> For months our endusers connected thru the SQL Server native driver for
> version 6. Now, have just ported the application to Powerbuilder 10,
> and I understand that the native drivers for SQL Server 2000 no longer
> exist in Powerbuilder, and you are expected to use OLEDB or ODBC.

I suppose that what you call "native drivers" is the old DB-Library
API, that I know that older versions of Powerbuilder used. MS has
deprecated this API, and have not made any development to it since
1998, so with DB-Lib you lack support for a lot of new stuff. All reason
to change.

> Thinking that OLEDB was the preferred method, I attempted to connect to
> the Server with this Profile in Powerbuilder. I could connect fine, but
> it frooze everyone else out. Anyone else have this problem, and if, how
> did you resolve it? So, some more questions:
> 1). What is the preferred way to connect to SQL Server 2000, OLEDB or
> ODBC.
> 2). What is the fastest connection?

It's not that OLE DB locks up the database by its own. There must be
something to it, but with zero knowledge of your environment, I have no
clue what it might be.

My prime choice would be SQLOLEDB to connect. But I need to add the
disclaimer that I have no experience of Powerbuilder, and it depends a
little on the API that Powerbuilder gives you. What you should not
use is OLE DB over ODBC, but make sure that you have Provider=SQLOLEDB
in your connectstring.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp