Recommended Approach
From: Dan Johnson (johnson_at_milehi.com)
Date: 11/10/05
- Next message: Andrew J. Kelly: "Re: SQL 2005 user limit"
- Previous message: Andrew J. Kelly: "Re: SQL 2005 user limit"
- Next in thread: Don Grover: "Re: Recommended Approach"
- Reply: Don Grover: "Re: Recommended Approach"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 10 Nov 2005 07:24:53 -0700
Our company has a web site hosted by a third party with a connection to our
SQL Server. The SQL Server resides locally behind the company's firewall.
We write software and would like to have our app (written primarily in VB6)
occasionally get small amounts of data from our SQL Server. For example,
when the customer/user wants to get the most recent update to our software,
we would want to retrieve the effective date of the user's subscription to
make sure they qualify for the update.
It is my understanding there are two approaches to doing this. One, we can
make a direct ADO connection from the user's PC to our SQL Server. Two, we
could (using RDS???) use our web sites connection to process the data
request, and return whatever info to the user's PC.
Both alternatives require opening up a port on our firewall to allow SQL
access (good, bad, ugly???). I would tend to think that using the first
alternative is preferable because it seems more efficient (if we're going to
open up the port, may as well streamline the user's connection as much as
possible...).
Can anyone point me in the right direction for analysis here? Would be
greatly appreciated!
Thanks
Dan
- Next message: Andrew J. Kelly: "Re: SQL 2005 user limit"
- Previous message: Andrew J. Kelly: "Re: SQL 2005 user limit"
- Next in thread: Don Grover: "Re: Recommended Approach"
- Reply: Don Grover: "Re: Recommended Approach"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|