Chapter 5. Client Connectivity

IN THIS CHAPTER

  • Enabling server connectivity

  • SQL Native Client development features

  • Client software connectivity

SQL Server 2008 follows Microsoft's philosophy of "secure by default" and reduces the surface area of the application. The initial installation allows local access only—no network connections for the Express and Developer editions (i.e., remote client applications will not be able to connect).

Note

Chapter 4, "Installing SQL Server 2008" discusses SQL Server surface area configuration as part of the installation process.

The Server Configuration Manager tool installed with SQL Server can nearly always communicate with SQL Server so you can configure the server connectivity options and open the server up for network access. The connectivity relies on open paths between the client and server machines. At times, there will be firewall issues to deal with.

With network access allowed on the SQL Server, SQL Server provides clients with a new means of accessing functionality and features through the new SQL Server Native Client (SNAC). Before getting into the SNAC, network access for the new server must be enabled.

Enabling Server Connectivity

When initially installed, SQL Server enables the Shared Memory protocol and disables the remaining protocols. This provides the greatest default security because only applications running locally to the SQL Server can connect.

To broaden SQL Server availability, additional network protocols must be enabled on the server. ...

Get Microsoft® SQL Server® 2008 Bible now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.