cliconfg, sql server client network configuration tool...펌

CLICONFG – The SQL Server Client Network Configuration Tool

 Add comments

Jan 052010

 

Did you know the wonderful world of cliconfg?

Many of you might not be aware of this little guy with big impact.

From Start –> RUN –> Cliconfg. and this is what you get.

The Client Network Utility lets you control, how Clients connects to SQL Server.

The protocol must be enabled on both the client and server to work.

On SQL Server go to SQL Server Configuration Manager –> Open the SQL Native Client Configuration –> click on Client Protocols and enable the desired protocol.

Named Pipes are good if the servers are within same domain/LAN and limited distance (Same City data centers Or about within 100 miles radius- good guess).

TCP/IP ( I call this as the SUPER PROTOCOL) is the king of protocols and can be used (should be used) across wide area networks (Example would be if you are located in New York city and your Database Server / Data Center is in Florida or Midwest or CA). in this scenario TCP/IP provides you the best Speed benefits.

Shared Memory Protocol, in lay mans terms, should be used if the database server resides on the same hardware as your client (example would be installing SQL Developer Edition on your desktop/laptop).

To Start with a simple example: Go to Alias Tab:

Click on ADD : Then select TCP/IP in Network libraries.

In the Server alias Text Box on TOP Write the SQL Server Name. and That’s it… Just click OK and you should be good to go.

Do these for the required Servers, Also if your SQL Server uses a different Port, uncheck the “Dynamically determine port” and write your SQL Server port number. If it is default 1433, leave it as it is.

Now that we have added the desired servers to the CLICONFG, now open the SQL Server Configuration Manager and check under SQL Native Client Configuration –> Aliases. all the Servers you listed in CLICONFG are listed here too.. see the inter-relation.