tailieunhanh - Microsoft SQL Server 2008 R2 Unleashed- P33

Microsoft SQL Server 2008 R2 Unleashed- P33:SQL Server 2005 provided a number of significant new features and enhancements over what was available in SQL Server 2000. This is not too surprising considering there was a five-year gap between these major SQL Server 2008 is not as much of a quantum leap forward from SQL Server 2005 | 274 CHAPTER 10 Client Installation and Configuration NOTE By default all network protocols except for VIA are enabled on the client during installation. That s all there is to installing SNAC Redistributing SNAC with Custom Client Applications If you build an application that relies on SNAC you need to be aware that it can be redistributed in two ways As part of any SQL Server 2008 installation or upgrade As a custom application installation dependency When you are building MSI files for an application it is important that you register as a package dependency and of course to install it as well if it is not present on the destination machine . This helps ensure that SNAC will not be accidentally uninstalled from the destination machine without first flashing a warning to users indicating that any application that relies on it will break. To do this you execute the following command early in your application s installation process msiexec i APPGUID unique identifier for your product NOTE The program name for SNAC found in the Add or Remove Programs Control Panel applet is Microsoft SQL Server 2008 Native Client not SQL Native Client as it is commonly known. Client Configuration Client configuration is a many-leveled beast consisting of operating system tasks such as installing protocols application tasks such as choosing or coding to a specific Application Programming Interface API provider or driver and maintenance tasks such as configuring network settings building connection strings and so on. The following sections cover a broad range of these tasks focusing on the most common. Many examples utilize TCP IP both because it is the default protocol for remote clients and because it is the most widely used. No chapter can cover all the possible ways of connecting but this one is designed to give you the tools you need to get set up right from the start and to navigate your way in case specific issues arise. The first client configuration tool