Date parsed: 27/09/2007 03:25:52
Date: Thu, 27 Sep 2007 10:25:52 -0700

Hi,

With SQL 2000, there was the "Connectivity Only" type of installation one
could perform on a client. Then you would have the "Client Network Utility"
program that you could use, e.g., to disable the client from using Named
Pipes when making connections to SQL 2000 instances.

What is the equivalent for SQL 2005? I tried installing only the "SQL
Native Client," but that did not leave and program I could find to control
the network protocol(s) used by the client.

--
Thank you,

Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org

Date parsed: 28/09/2007 02:44:28
Date: Fri, 28 Sep 2007 02:44:28 GMT

Hi Daniel,
In SQL Server 2005, the original Client Network Utility (cliconfg.exe) has
been integrated into SQL Server Configuration Manager which contains both
server configuration and client configuration (named SQL Native Client
Configuration). If you want to use the feature, you can install the Client
Tools (Management Tools) from your SQL Server 2005 setup CD.
You may also refer to:
Client Network Configuration
http://technet.microsoft.com/en-us/library/ms190611.aspx

If you have any other questions or concerns, please feel free to let me
know. It is my pleasure to be of assistance.

Best regards,
Charles Wang
Microsoft Online Community Support

======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

Date parsed: 28/09/2007 11:15:51
Date: Fri, 28 Sep 2007 09:15:51 +0200

Charles,

I don't recommend installing something on the machine to get a tool which does some modifications in
the registry when there already exists such a tool on the machine. My point is that the machine
already has cliconfg.exe on the machine, so why bother installing another tool which does the same
thing?

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Charles Wang[MSFT]" <changliw@online.microsoft.com> wrote in message
news:Z3WFKmXAIHA.5972@TK2MSFTNGHUB02.phx.gbl...
> Hi Daniel,
> In SQL Server 2005, the original Client Network Utility (cliconfg.exe) has
> been integrated into SQL Server Configuration Manager which contains both
> server configuration and client configuration (named SQL Native Client
> Configuration). If you want to use the feature, you can install the Client
> Tools (Management Tools) from your SQL Server 2005 setup CD.
> You may also refer to:
> Client Network Configuration
> http://technet.microsoft.com/en-us/library/ms190611.aspx
>
> If you have any other questions or concerns, please feel free to let me
> know. It is my pleasure to be of assistance.
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
>
> ======================================================
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================
>
>

Date parsed: 19/10/2007 06:41:51
Date: Fri, 19 Oct 2007 13:41:51 -0700

Hi,

Thanks guys. Still, with SQL 2005 is there any way to install just the SQL
Server Configuration Manager? I don't want to load down our Web server
installs with the all the stuff that comes with the full suite of client
tools.

--
Thank you,

Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org



"Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in
message news:A741F84A-2155-4A6B-A647-668EDC03ABDD@microsoft.com...
> Thanks for alerting me on those issues, Charles. I haven't heard about
> such.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
>
> "Charles Wang[MSFT]" <changliw@online.microsoft.com> wrote in message
> news:PUecPUbAIHA.5972@TK2MSFTNGHUB02.phx.gbl...
>> Hi Tibor,
>> I know that installing the tool is not necessary. I just would like to
>> let
>> Daniel know that SQL Server 2005 has a new tool to replace the older
>> Client
>> Network Utility. Also there is a reason which is for avoiding some
>> potential issues for SQL Native Client connections. Actually I indeed saw
>> that in some cases CLICONFIG did not take effect for SQL Native Client
>> connections. For example, an alias configured in cliconfg.exe did not
>> take
>> effect for SQL Native Client connections and the issue was eventually
>> resolved by adding an alias in SQL Native Client Configuration. Of
>> course
>> there is another way to resolve this issue by manually modifying
>> registry,
>> but this way is not very friendly.
>>
>> Since SQL Server 2005 Client Tools is redistributable and SQL Server
>> Native
>> Configuration is a replacement for the old Client Network Utility, it
>> should be also fine to install it on a client, though it is not
>> necessary.
>> I think that if SQL Native Client setup program directly include the tool
>> as well as MDAC including cliconfig.exe, you would not have the concern
>> here. :)
>>
>> Have a nice day!
>>
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>>
>> ======================================================
>> When responding to posts, please "Reply to Group" via
>> your newsreader so that others may learn and benefit
>> from this issue.
>> ======================================================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> ======================================================
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>