Question on Connectivity tools for SQL 2000 and SQL 2005

Question on just connectivity tools for SQL 2000 and SQL 2005
We are in the process of doing a inplace-upgrade of our SQL Server 2000
to SQL Server 2005. Currently all of the client computers have only the
connectivity tools from SQL 2000 installed in them. Is it necessary to
upgrade all the client machines with new SQL 2005 connectivity tools?
Any advice in this regard will be greatly appreciated.
Question on Client tools for SQL 2000 and SQL 2005
The other question I have is I have a unique client that has SQL 2000
Client tools installed, I am planning to also install the SQL 2005
Client tools, in this scenario when the Client connects to the Server
which client setting does it take. So for instance if in the SQL
Serever 2000 Network Client utility if I have only tcp_ip enabled as
the network protocol and on SQL 2005 if I have only Namedpipes enabled,
how does SQL Server figure out which setting should it look at? Do I
need to keep them consistent for both?
Thanks
Hi
Without upgrading the clients you will not have access to the facilities
available to the Native Client although this may not be a problem immediately
after upgrading.
Depending on what you require the client tools for, then you may not need to
upgrade them, but you will not have any of the SQL 2005 specific features
available. The protocol used by your application will depend on what you have
specified in the connection string, installing SQL 2005 may give you more
updated versions of the component you use.
If you are not using SQL 2000, I would look at removing the SQL 2000 tools.
HTH
John
"shub" wrote:

> Question on just connectivity tools for SQL 2000 and SQL 2005
> We are in the process of doing a inplace-upgrade of our SQL Server 2000
> to SQL Server 2005. Currently all of the client computers have only the
> connectivity tools from SQL 2000 installed in them. Is it necessary to
> upgrade all the client machines with new SQL 2005 connectivity tools?
> Any advice in this regard will be greatly appreciated.
> Question on Client tools for SQL 2000 and SQL 2005
> The other question I have is I have a unique client that has SQL 2000
> Client tools installed, I am planning to also install the SQL 2005
> Client tools, in this scenario when the Client connects to the Server
> which client setting does it take. So for instance if in the SQL
> Serever 2000 Network Client utility if I have only tcp_ip enabled as
> the network protocol and on SQL 2005 if I have only Namedpipes enabled,
> how does SQL Server figure out which setting should it look at? Do I
> need to keep them consistent for both?
> Thanks
>