1. In order to access SQL Server Configuration Manager do this:
Start >> Programs >> Microsoft SQL Server 2005 >> Configuration Tools >> SQL Server Configuration Manager
2. Services pertaining to SQL Server would be available inside this tool under the heading "SQL Server 2005 Services".
This is only for easy access, as these "Services" are still available (as it was all this days!) within Control Panel >> Administrative Tools >> Services.
3. This tool has Server and Client Network configuration services.
Net libraries facilitate IPC (Interprocess Communication) exchange of information between Client and Server.
In SQL 2005 we have four ways (Protocol names) by which IPC can take place. They are "Shared Memory", TCP/IP", "Named Pipes" and "VIA". All other legacy protocols which were there till SQL Server 2000 have been removed.
Let me explain the 2 ways which are popularly in use :)
Shared Memory -- If "Client" and "Server" are on the same box then this is the preferred method way.
TCP/IP -- Faster way of communicating between the "Client" and "Server". It uses the port 1433.
Protocol priorities OR order can be specified. That is, for an example, Client can set "NamedPipes" as 1 and "TCP/IP" as 2. Meaning, first try to communicate with the server using "Named Pipes". If it is closed on the Server end then it would try "TCP/IP".
4. Irrespective of any number of SQL instances you have in a system there would be ONLY ONE Configuration Manager.
- In SQL Server 2005, SQL Server can listen to more than one "Ports" now. Till SQL Server 2000, this wasn't possible, it could listen to only one Port.
- Now Access can be controlled on Port Level (i.e., HTTPEndPoint)