【正文】 ? 嘗試指定 SQL Server 實(shí)例正在偵聽(tīng)的特定端口。? 如果你正從運(yùn)行 SQL Server 的計(jì)算機(jī)進(jìn)行連接，可以指定“.”或“（本地）”（不帶引號(hào)）取代服務(wù)器名稱(chēng)，然后連接。? 在 %systemroot%\system32\drivers\etc\hosts 文件中添加一個(gè)與正在運(yùn)行 SQL Server 實(shí)例的計(jì)算機(jī)的 IP 地址相應(yīng)的條目。例如，如果 TCP/IP 連接失敗，則命名管道連接成功。你可以為使用該協(xié)議的 SQL Server 實(shí)例創(chuàng)建一個(gè)新的別名，從而指定不同的協(xié)議。? 從其他數(shù)據(jù)源（例如 ODBC DSN、.udl 文件、SQL 查詢分析器、SQL Server 企業(yè)管理器，isql 實(shí)用程序或 OSQL 實(shí)用程序）測(cè)試到 SQL Server 實(shí)例的連接。測(cè)試連接到 SQL Server 實(shí)例的不同方法當(dāng)你連接到 SQL Server 實(shí)例時(shí)，如果遇到了連接問(wèn)題，可以使用下面的一種或多種方法來(lái)解決連接問(wèn)題。在此時(shí)間內(nèi)嘗試連接到 SQL Server 的客戶端可能會(huì)收到一條與以下類(lèi)似的錯(cuò)誤信息： Timeout ExpiredSQL Server 代理服務(wù)可能無(wú)法啟動(dòng)，這是因?yàn)樗却?SQL Server 恢復(fù)數(shù)據(jù)庫(kù)。當(dāng)停止 SQL Server 實(shí)例時(shí)，SQL Server 還將前滾已提交的事務(wù)和沒(méi)有寫(xiě)入硬盤(pán)的更改。4. 在命令提示符下，運(yùn)行下列命令（此處的 IP address 就是你在步驟 3 中記錄的 IP 地址）解決在恢復(fù)過(guò)程中連接超時(shí)的問(wèn)題在每次啟動(dòng)一個(gè) SQL Server 實(shí)例時(shí)，SQL Server 將恢復(fù)各個(gè)數(shù)據(jù)庫(kù)。2. 在“運(yùn)行”對(duì)話框中，在“打開(kāi)”框中鍵入 cmd，然后單擊“確定”。如果名稱(chēng)解析程序不正確地工作，SQL服務(wù)器的實(shí)例不是可到達(dá)的，你可能接受到一條或多條下列錯(cuò)誤信息：SQL Server does not exist or access deniedGeneral Network ErrorCannot Generate SSPI Context為了要確認(rèn)名稱(chēng)解析程序是解析正確的服務(wù)器，你能使用服務(wù)器的服務(wù)器名字和IP地址ping服務(wù)器。對(duì)于關(guān)于SQL Server通訊部件和網(wǎng)絡(luò)庫(kù)的其它信息，請(qǐng)參見(jiàn)“SQL Server 在線參考書(shū)”中的下列主題： ? 通信部件? 客戶端和服務(wù)器網(wǎng)絡(luò)庫(kù)? 管理客戶端解決連接問(wèn)題在 SQL Server 2008 中大多數(shù)連接問(wèn)題你可能會(huì)注意到的都是由 TCP/IP 的問(wèn)題或 Windows 身份認(rèn)證的問(wèn)題引起，或者兩者共同組合引起。如此，SQL Server 2008 啟用并偵聽(tīng) TCP/IP、命名管道和共享內(nèi)存。在安裝 SQL Server 安裝程序中的服務(wù)器工具期間，服務(wù)器的網(wǎng)絡(luò)庫(kù)也被同時(shí)安裝了。東華理工大學(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 p