|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Today @ 8:08 AM
Points: 17,
Visits: 175
|
|
Hi there,
Could anybody tell me in what way the communication between client and SQL Server is effected by client side configuration through the SQL Server Client Network utility (C:\WINDOWS\system32\cliconfg.exe).
The default configuration does not have any protocols enabled. Is native SQL communication still possible?
Kind regards,
Dave
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 4:49 AM
Points: 1,075,
Visits: 5,119
|
|
Hi Dave,
Above utility belongs to SQL Server 2000 version.
SQL Server Configuration Manager utility is used for SQL Server 2008 version.
Without enabling any protocol communication is not possible.
Regards,
Suresh
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Today @ 8:08 AM
Points: 17,
Visits: 175
|
|
Hi Suresh,
Thanx for the quick reply.
Is the new client utility installed as a default OS component like the 2000 version or does is need a seperate client installation? If this component does need a separate client installation, would this always be the adviced approach in order to make sure the latest driver versions en configuration tools are used?
Kind regards,
Dave
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 4:49 AM
Points: 1,075,
Visits: 5,119
|
|
SQL Server client software is not part of OS. It needs to be installed separately. Service Pack is applicable to client tools also.
Regards
|
|
|
|