【正文】 東華理工大學(xué)2013屆本科生畢業(yè)設(shè)計(jì)（論文）外文翻譯 外文2How to troubleshoot connectivity issues in SQL Server 2008After you install SQL Server 2008, you can configure the properties of the client NetLibraries by using Client Network Utility. You can configure the properties of the server NetLibraries by using Server Network Utility (). The server NetLibraries are installed during the installation of the server tools in SQL Server Setup. However, some of the server NetLibraries may not be active. By default, SQL Server 2008 enables and listens on TCP/IP, named pipes, and Shared Memory. Therefore, for a client to connect to a server puter, the client must connect by using a client NetLibrary that matches one of the server NetLibraries that is currently being used by the instance of SQL Server.For additional information about SQL Server munication ponents and NetLibraries, see the following topics in SQL Server Books Online: ? Communication Components? Client and Server NetLibraries? Managing ClientsTroubleshoot connectivity issuesMost of the connectivity issues that you may notice in SQL Server 2008 occur because of problems with TCP/IP, Windows authentication, or a bination of TCP/IP and Windows authentication. Verify your DNS settingsThe name resolution process in Domain Name System (DNS) is used to resolve the IP address to the name of the instance of SQL Server. If the name resolution process does not work correctly, the instance of SQL Server is not reachable, and you may receive one or more of the following error messages: SQL Server does not exist or access deniedGeneral Network ErrorCannot Generate SSPI ContextTo verify that the name resolution process is resolving the correct server, you can ping the server by using the server name and the IP address of the server. To do so, follow these steps: 1. Click Start, and then click Run.2. In the Run dialog box, type cmd in the Open box, and then click OK.3. At the mand prompt, run the following mand:ping Server NameNote the IP address that is returned.4. At the mand prompt, run the following mand (where IP address is the IP address that you noted in step 3)Troubleshoot connections that time out during the recovery processEvery time that you start an instance of SQL Server, SQL Server recovers each database. During this recovery process, SQL Server rolls back the transactions that are not mitted. SQL Server also rolls forward the transactions that are mitted and the changes that were not written to the hard disk when the instance of SQL Server was stopped. When the recovery process is plete, SQL Server logs the following message in the SQL Server error log file: Recovery CompleteDuring the recovery process, SQL Server may not accept connections. Clients that try to connect to the instance of SQL Server during that time may receive an error message that is similar to the following: Timeout ExpiredThe SQL Server Agent service may not start because it waits for SQL Server to recover the databases. Therefore, when you receive the following message in the SQL Server error log file, the connections will no longer fail with a timeout error: Recovery CompleteIf the recovery process takes a long time, you may have to additionally troubleshoot the recovery process.Test different ways to connect to the instance of SQL ServerIf you experience connectivity problems when you connect to the instance of SQL Server, you can use one or more of the following methods to work around the connectivity problem. ? Test the connectivity to the instance of SQL Server by using both SQL Server Authentication and Windows authentication.? Test the connectivity to the instance of SQL Server from other data sources, such as an ODBC DSN, a .udl file, SQL Query Analyzer, SQL Server Enterprise Manager, the isql utility, or the osql utility.? Test the connectivity to the instance of SQL Server by using different protocols. You can specify different protocols by creating a new alias for the instance of SQL Server using that protocol. You can also specify the protocol in your connection string by adding tcp:, np:, lpc:, or rpc: to the beginning of the name of the instance of SQL Server. For example, if TCP/IP connections are not successful, named pipes connections succeed.? Test the connectivity by using a different login account to help you determine if the problem is associated with a particular login account.? Try to add an entry that corresponds to the IP address of the pute