remote server

[koredump]

Hi All,
I'm working on an distributable application that will have to connect to a
remote sql server over the internet and would like to find out what will be
the best way to implement this type of a connection.

I've been googling for hours now and can't find a straight answer as to what
is the best way connect to remote SQL server. In the past I've been
connecting directly to remote server that had a listening port opened. But I
gathered, connecting directly is not a very safe approach. I will be using
..net remoting in my application and thought about using it for my data tier
needs as well. I could also use webservices, and now I hear that MS SQL
Server 2005 can be HTTP listener and expose a webservice to allow the
execution of statements and sql procedures. What's the best way? Does
someone know of a good article that will provide me with some guidance?
Should I just connect direclty using ado.net without an abstraction layer
between the application and the server?

TIA for any help

rich

 

[William \(Bill\) Vaughn]

The safest way (by far) is to open a VPN channel to the SS host
server/domain. If you can connect via an open TCP port so can I (and most
everyone else).


--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

 

[Cor Ligthert [MVP]]

Hi Bill,

Where have you been, I missed you already. I was thinking about that
yesterday.

Are you busy with your new book. There is so much new in my opinion that it
needs almost a complete new approach in ADONET.



Cor

 

[koredump]

Thank you for your reply William. Unfortunately, I can't use VPN. This is
suppose to be a smart client application and VPN would only introduce
another level of user support (not to mention the cost involved). Therefore,
if I can't use VPN, what would would be the next best option. There could be
hundreds of user connecting to this database, most will only retrieve/insert
a few records per session. I'm leaning towards using .net remoting,
especially since in .net 2.0 they've added to capability to create a secure
TCP channel. Webservices, on the other hand, are very easy to implement but
also are not as capable as remoting. Unfortunately, I don't have any viable
experience in using either one of the technologies when it comes to working
with a SQL server. Looking for some helpful advice...

TIA,

Rich

 

[William \(Bill\) Vaughn]

What you're describing is best implemented with an ASP application--not with
client/server. CS is designed for dedicated networks or where a VPN is a
viable alternative.

Incidentally, I've been heads down on my new book (just topping off the
"Intro to Visual Studio" (Server Explorer, Query Builder etal.) chapter). It
alone is pushing 100 pages so it will doubtless be 2-3 chapters.

I also just came back from a tour of Australia and New Zealand.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________