Accessing SQL server db through the Internet...

Hi there I'm wondering if it does make any sense to access data from a MS
SQL Server 2000 over the Internet.

ASP pages hosted by my ISP must load from db article abstracts (10 per page)
but the DB is located elsewhere, so the ASP code must acces remotely the db.

1) Is it possible?

2) Does it makes any sense, or it will be very slow?

3) Any drawbacks, like exposing the db to the Internet? (Risks)

4) How do you acheive that? Code sample.

Thanks to anyone wishing to help

Regards!

Re: Accessing SQL server db through the Internet...

"Atlas" wrote in message
news:12r9vg1ddq2sld4@news.supernews.com...
> Hi there I'm wondering if it does make any sense to access data from a MS
> SQL Server 2000 over the Internet.
>
> ASP pages hosted by my ISP must load from db article abstracts (10 per
> page) but the DB is located elsewhere, so the ASP code must acces remotely
> the db.
>
> 1) Is it possible?
>
> 2) Does it makes any sense, or it will be very slow?
>
> 3) Any drawbacks, like exposing the db to the Internet? (Risks)
>
> 4) How do you acheive that? Code sample.
>

1. Yes you can access a SQL Server database remotely.
2. In all likelihood, it will be slower. Any time you cross networks, a
delay will be introduced. How this manifests itself can only be determined
by testing.
3. Whether it's hosted locally (to your application) or remotely won't
affect security.
4. You will find connection advice here:
http://www.carlprothman.net/Default.aspx?tabid=87#OLEDBProvi derForSQLServer

--
Mike Brind

Re: Accessing SQL server db through the Internet...

"Atlas" wrote in message
news:12r9vg1ddq2sld4@news.supernews.com...
> Hi there I'm wondering if it does make any sense to access data from a MS
> SQL Server 2000 over the Internet.
>
> ASP pages hosted by my ISP must load from db article abstracts (10 per
> page) but the DB is located elsewhere, so the ASP code must acces remotely
> the db.
>
> 1) Is it possible?
>
> 2) Does it makes any sense, or it will be very slow?
>
> 3) Any drawbacks, like exposing the db to the Internet? (Risks)
>
> 4) How do you acheive that? Code sample.
>
> Thanks to anyone wishing to help

I'm doing this very thing for a customer. This is the setup.

The web site is remote. It make an HTTP request to an .asp page on a remote
server. That server only accepts outside connectivity from the IP address
of the web server making the request on a specified port. It calls a
default page which makes and ADO connection to the SQL server sitting right
next to it, calling a stored procedure, which returns and XML file, which is
returned to the original web server that uses an XLT to display the result.

The reason it was setup this way is because we took a commercial app that
the users use privately and allowed a portion of it to be displayed on a
public web server. It's a job search type site like monster.com.

The only issue we ran into dealt with the application which on a daily
basis, removes all users in the SQL server that have access to its database
and recreates them. They did this so other couldn't write 3rd party apps to
access their data. We got around it by creating the user in the app.

Since we don't pass any credentials across the net, we didn't have a need to
make it an SSL connection which would have slowed it down. The credentials
are passed only on the private network to the SQL server running in mixed
mode.

HTH...

--
Roland Hall