database connection

[SOC]

I am familiar with connecting asp pages to sql server when both servers are
on a LAN.

Can anyone advise on how to connect when the servers are remote from each
other?

Thanks Soc.

 

[Patrick]

Well, you CAN do that but the question is why would you want to? You can
specify any server in your ODBC connection string, it doesn't have to be a
server on your local network.

So if the connection string on your private LAN looks something like this:
"Driver={SQL
Server};Server=10.1.1.10;Database=SOMEDB;UID=dbuser;pwd=dbpassword"

then connecting to a remote server with a public IP of 140.192.1.10 would
look like this:
"Driver={SQL
Server};Server=140.192.1.10;Database=SOMEDB;UID=dbuser;pwd=dbpassword"

Doing this would require that port 1433 be accessible remotely, which
presents its own set of security concerns. But the worst part is the
latency. Even if your remote location can upload at a full T1 speed of
1.5mbps... even a DS3 at 44mbps, that's woefully short of the 100mbps or
1gbps speeds of a typical LAN.

 

[SOC]

Thanks Patrick. This is very helpful.
Soc

Well, you CAN do that but the question is why would you want to? You can
specify any server in your ODBC connection string, it doesn't have to be a
server on your local network.

So if the connection string on your private LAN looks something like this:
"Driver={SQL
Server};Server=10.1.1.10;Database=SOMEDB;UID=dbuser;pwd=dbpassword"

then connecting to a remote server with a public IP of 140.192.1.10 would
look like this:
"Driver={SQL
Server};Server=140.192.1.10;Database=SOMEDB;UID=dbuser;pwd=dbpassword"

Doing this would require that port 1433 be accessible remotely, which
presents its own set of security concerns. But the worst part is the
latency. Even if your remote location can upload at a full T1 speed of
1.5mbps... even a DS3 at 44mbps, that's woefully short of the 100mbps or
1gbps speeds of a typical LAN.

 

[Mike Brind]

Well, you CAN do that but the question is why would you want to?

Needing to connect to a remote instance is not an uncommon requirement.

You can specify any server in your ODBC connection string

You would be better advised to use OLEDB for SQL Server. ODBC just adds an
additional layer of software:

Provider=sqloledb;Data Source=140.192.1.10,1433;Network
Library=DBMSSOCN;Initial Catalog=someDB;User ID=Username;Password=Password;

 

[SOC]

Thanks Mike.

Needing to connect to a remote instance is not an uncommon requirement.


You would be better advised to use OLEDB for SQL Server. ODBC just adds an
additional layer of software:

Provider=sqloledb;Data Source=140.192.1.10,1433;Network
Library=DBMSSOCN;Initial Catalog=someDB;User ID=Username;Password=Password;