Best Protocol?

What is the best protocol (Named Pipes, TCP/IP or VIA) to use when connecting to a SQL Server 2005 on:

a) LAN (100MBps+)

b) VPN (via Internet)

c) Internet

And why?

The answer you're looking for is here.
http://msdn2.microsoft.com/en-us/library/ms187892.aspx|||

I do not believe the article about choosing a connection type to the server answers the question.

In my opinion it is ovbious that the LAN is the best just because of the TCP/IP connection method being able to take advantage of low overhead, hi bandwidth connections.

VPN is guaranteed to be slower than the LAN because the protocol is sitting on top of TCP/IP and will inherently add more overhead.

As far as Internet goes, I am not sure what the difference b/w LAN and Internet is going to be as far as which protocol to use.

Hope this helps.

|||

oj (MVP): Your comment was very helpfull, thank you. I had trouble finding this article myself.

Leifton: Yours was not so.

From what I understand, this is my conclusion (in a very cut-down nutshell).

VIA works best with VIA hardware, enough said.

Named Pipes works best over normal LAN.

TCP/IP works best over VPN and Internet.

Best Protocol?

What is the best protocol (Named Pipes, TCP/IP or VIA) to use when connecting to a SQL Server 2005 on:

a) LAN (100MBps+)

b) VPN (via Internet)

c) Internet

And why?

The answer you're looking for is here.
http://msdn2.microsoft.com/en-us/library/ms187892.aspx|||

I do not believe the article about choosing a connection type to the server answers the question.

In my opinion it is ovbious that the LAN is the best just because of the TCP/IP connection method being able to take advantage of low overhead, hi bandwidth connections.

VPN is guaranteed to be slower than the LAN because the protocol is sitting on top of TCP/IP and will inherently add more overhead.

As far as Internet goes, I am not sure what the difference b/w LAN and Internet is going to be as far as which protocol to use.

Hope this helps.

|||

oj (MVP): Your comment was very helpfull, thank you. I had trouble finding this article myself.

Leifton: Yours was not so.

From what I understand, this is my conclusion (in a very cut-down nutshell).

VIA works best with VIA hardware, enough said.

Named Pipes works best over normal LAN.

TCP/IP works best over VPN and Internet.

Best approach to updating remote server?

I have a local production server, and a web server at a remote ISP connected
via a VPN. Both servers are running MS SQL 2000. I wish to do an extract
of data on the production server and update it to the web server daily. The
web server only gets a subset of the information on the production server.
I know I can't be the first to need this so what I am searching for is the
best way to accomplish this. Do I refresh the web server daily (about 500MB
of data)? Should I send each table with an indicator as to
Add/Change/Delete, and write a procedure to import? or is there just another
solution I am overlooking.
Any suggestions would be appreciated.
TIA, MarkHi Mark.
A common approach to achieving this is to create a DTS package that
encapsulates the process, applies business rules to the data etc & then
schedule it to run from the local production server. I've done this with
various ISP hosted SQL databases with fairly good success.
Is your ISP hosted SQL Server dedicated or shared? If dedicated, many
options may open up to you that a shared server might have available.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Mark Butler" <mredhat_nospam@.yahoo.com> wrote in message
news:enU%238d8DEHA.2932@.tk2msftngp13.phx.gbl...
> I have a local production server, and a web server at a remote ISP
connected
> via a VPN. Both servers are running MS SQL 2000. I wish to do an extract
> of data on the production server and update it to the web server daily.
The
> web server only gets a subset of the information on the production server.
> I know I can't be the first to need this so what I am searching for is the
> best way to accomplish this. Do I refresh the web server daily (about
500MB
> of data)? Should I send each table with an indicator as to
> Add/Change/Delete, and write a procedure to import? or is there just
another
> solution I am overlooking.
> Any suggestions would be appreciated.
> TIA, Mark
>