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 Practices/Provider connecting to an Oracle Database?

Are there generalized best practices with regards to which method/provider to use when accessing an Oracle database? I have used both the "Native OLE DB\Microsoft OLE DB Provider for Oracle" and the "Native OLE DB\Oracle Provider for OLE DB" and both seem to have their own quirks (requirement to convert to Unicode, etc) but I also have heard that I shouldn't be using an "OLE DB" source at all, but to set it up as an ADO .Net connection.

We are just beginning to implement SSIS, and are trying to establish Best Practices/Standards etc.

Are there any gotchas - performance and/or otherwise I should know about?

Thanks in advance!

I'm assuming you've looked at the SSIS Connectivity whitepaper at http://ssis.wik.is/File:Connectivity_White_Paper/Connectivity_and_SQL_Server_Integration_Services_forum_post.doc (Oracle connectivity section).

We have plans to benchmark connectors in the future, when we might be able to share best practices and performance stats.

Best practices for remotely connecting

I have a Windows 2003 standard edition server with MSDE 2000 installed
at a client. I would like to be able to connect my SQL Enterprise
manager in case I need to do something in their database and I need to
do it remotely. I have the MSDE set to mixed mode authentication and
opened the ports (1433 and tried 2433 as well because client network
utility said it used that port) but I cannot connect for some reason.
Any clues what I still need to do?
The other question is: is it safe to connect a SQL server directly to
the net? The SQL Server is fully up to date with the latest patches.
Are there any guidelines that I need to follow when I want to do this
(in a safe way)?
Thanks in advance,
Stijn Verrept.You should consider establishing a VPN connection from your remote client.
Then use Terminal Server or Remote Desktop to administer the server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] wrote:

quote:

---

> You should consider establishing a VPN connection from your remote
> client. Then use Terminal Server or Remote Desktop to administer the
> server.

---

Thanks for your answer Kevin. I can login with TS but MSDE does not
include enterprise manager so I cannot install this on the clients pc!
Kind regards,
Stijn Verrept.|||So, unless the client as a Terminal Server that you can install the SQL
Client tools, your options are limited.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] wrote:

quote:

---

> So, unless the client as a Terminal Server that you can install the
> SQL Client tools, your options are limited.

---

What do you mean? The client is running a terminal server. And I can
log in on that machine. The problem is that it does not have
Enterprise manager. This is why I need to connect with my enterprise
manager to the terminal server through the net. Isn't this possible?
Why doesn't it want to work?
Kind regards,
Stijn Verrept.|||Here's what I'm recommending:
1. Client -->VPN -->Terminal Server (with Enterprise Manager Installed)
-->MSDE
or
2. Client (with Enterprise Manager) -->VPN -->MSDE
Option 1 would be preferred.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Im having exactly the same problem.
However, we need access to both our SQL Server and their Server as we
do database design work as part of our web development and need to
upload databases we have created.
Weve tried the VPN route, but our policy is to keep our SQL Server
well behind the firewall, and there are no exceptions (Clients company
information kept on them so security is a big deal) so they cant see
our DB.
They have opened all ports for our IP address so all traffic is
allowed, but we can still not connect to their DB.
A simple yes or no is required, Can you connect to a remote MSDE
Server across the internet and register it in SQL Server Enterprise
manager?
TCPIP and Named Pipes are Installed and enabled on MSDE
kevmc@.online.microsoft.com (Kevin McDonnell [MSFT]) wrote in message news:<v40lyXs2DHA.3564@.cp
msftngxa07.phx.gbl>...
> Here's what I'm recommending:
> 1. Client -->VPN -->Terminal Server (with Enterprise Manager Installed)
> -->MSDE
> or
> 2. Client (with Enterprise Manager) -->VPN -->MSDE
> Option 1 would be preferred.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.|||Can you connect to a remote MSDE
Server across the internet and register it in SQL Server Enterprise
manager?
Simple Answer:
Yes. Over TCP. As long as the ports are open on the firewall.
287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin, Thats what I thought, but not what I wanted to hear!
This means we have a different problem which is going to be a nightmare
to sort out.
If SQL Server (MSDE) has the TCPIP netlib enabled and the default port
is being used (1433), do we need to have 1433 enabled on both firewalls
(theirs and ours) to enable enterprise manager to register this server?
Also, Do we need to open port 1434 (Ive heard that this is needed for 2
way communication)
Any other ideas why I can connect to our ISP hosted SQL Servers, but not
our clients (who hosts their own website) even though they have tried
with the server outside the firewall? Even If I make a vpn connection to
the SQL Server box, and can ping it by name, I still cant connect. I get
the error:
SQL Server does not exist or access is denied
ConnectionOpen(Connect())
Desperate to get this sorted now
Thanx again
remove 'REMOVESPAM.' for email
Karl Rhodes
Internet Solutions Architect
The Learning Business & Keywave
www.thelearningbiz.com
www.keywave.com
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||from previous post:
"This means we have a different problem which is going to be a nightmare
to sort out.
If SQL Server (MSDE) has the TCPIP netlib enabled and the default port
is being used (1433), do we need to have 1433 enabled on both firewalls
(theirs and ours) to enable enterprise manager to register this server?
Also, Do we need to open port 1434 (Ive heard that this is needed for 2
way communication)"
You would need 1433 open on the remote firewall. You client would open up
a tcp session to 1433 and communicate back to your
client on a random tcp port.
Ex. client opens port 2000 and sends traffic to the remote MSDE on 1433
The communication comes back from 1433 to your client port 2000.
"Any other ideas why I can connect to our ISP hosted SQL Servers, but not
our clients (who hosts their own website) even though they have tried
with the server outside the firewall? Even If I make a vpn connection to
the SQL Server box, and can ping it by name, I still cant connect. I get
the error:
SQL Server does not exist or access is denied
ConnectionOpen(Connect())
"
This error is meaningless without the OS error number.
Force a TCP sockets connection with ISQL.exe
Ex. ISQL -Stcp:ServerName -Uuserid -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sql

best practice connecting to run database creation script

I want to run a database creation sql script. The problem (I believe) is
that I have to specify the database I wish to connect to when connecting to
the server (ADO). Should I specify the Main database? Or is there a way
around this?
You can use master for the initial catalog in your
connection string.
-Sue
On Mon, 7 Nov 2005 13:01:03 -0800, "William Sullivan"
<WilliamSullivan@.discussions.microsoft.com> wrote:

>I want to run a database creation sql script. The problem (I believe) is
>that I have to specify the database I wish to connect to when connecting to
>the server (ADO). Should I specify the Main database? Or is there a way
>around this?

best practice connecting to run database creation script

I want to run a database creation sql script. The problem (I believe) is
that I have to specify the database I wish to connect to when connecting to
the server (ADO). Should I specify the Main database? Or is there a way
around this?You can use master for the initial catalog in your
connection string.
-Sue
On Mon, 7 Nov 2005 13:01:03 -0800, "William Sullivan"
<WilliamSullivan@.discussions.microsoft.com> wrote:

>I want to run a database creation sql script. The problem (I believe) is
>that I have to specify the database I wish to connect to when connecting to
>the server (ADO). Should I specify the Main database? Or is there a way
>around this?

BDE admin connecting problem, How do I connect via IP address.

Hi, I am connecting from clientside with sql server 2005 installed trying to connect to a database running on a server with sql server 2000 installed. this is not a 2000 to 2005 compatibility issue.
I can connect locally fine to the server and log in using the sa account, however for BDE admin i HAVE to use the server name instead of ip address. If i try to use the ip address of the server, the connection dosnt get established. *this is all happening localy on our own network.

How to I use ip address to connect instead of the server name? I will need to connect remotely outside of our network later on, and i dont think I can use the servername. Does anyone have a solution? thanks.BDE = borland database engine|||I suggest creating an ODBC DSN and using that from BDE rather than the SQLLINK driver|||thanks for the input, we figured out the problem though, it seems the server uses a proprietary listening port, say.. "3314" set up for their server. we were able to connect after setting up an alias for sql server.|||I have more questions

1) does SQL server 2005 come with a client only tool?
2) is there a way to connect via an alias with an application without installing sql server 2005?

thanks in advance!|||

1/ Yes its called SQL Server Management Studio (or Express Edition of SSMS) for management and there are dev tools, config tools etc

2/ you need to install SQL Server Computer Manager to config alias's

BDE 5.01 not connecting to SQL2K after patching

Hello All,
I am experiencing unusual behaviour with a number of desktops (3 of 20) running the BDE and the SQL connectivity option from the sql cd. For reasons unknown the BDE suddenly stops connecting to the database and cant be fixed without a reimage. Appears t
o be a key or dll that is causing interoperability issues.
No idea what o/s patch is causing trouble at this stage but its a recent phenomena.
has anyone seen this type of behaviour with third part software using BDE/SQL connectivity ?
Brian in AU
+61 431 479 751
What error do you get?
Could the problem be something along these lines?
259569 PRB: Installing Third-Party Product Breaks Windows 2000 MDAC Registry
http://support.microsoft.com/?id=259569
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.