SQL Server 2012 版本資訊SQL Server 2012 Release Notes

適用於: 是SQL Server 否Azure SQL Database 否Azure Synapse Analytics (SQL DW) 否平行處理資料倉儲 APPLIES TO: yesSQL Server noAzure SQL Database noAzure Synapse Analytics (SQL DW) noParallel Data Warehouse

這份版本資訊文件將描述有關您安裝或疑難排解 Microsoft SQL Server 2012 (請按一下這裡下載) 之前應該閱讀的已知問題。This Release Notes document describes known issues that you should read about before you install or troubleshoot Microsoft SQL Server 2012 (click here to download it). 這份版本資訊文件僅於線上提供,安裝媒體中並不提供,而且會定期更新。This Release Notes document is available online only, not on the installation media, and it is updated periodically.

如需有關如何開始使用和安裝 SQL Server 2012 的詳細資訊,請參閱 SQL Server 2012 讀我檔案。For information about how to get started and install SQL Server 2012, see the SQL Server 2012 Readme. 您可以從安裝媒體與 讀我檔案 下載頁面,取得讀我檔案文件。The Readme document is available on the installation media and from the Readme download page. 您也可以在 SQL Server 線上叢書SQL Server 論壇中尋找更多資訊。You can also find more information in SQL Server Books Online and on the SQL Server Forums.

1.0 安裝之前1.0 Before You Install

在安裝 SQL Server 2019 (15.x)SQL Server 2019 (15.x)之前,請考量以下資訊。Before installing SQL Server 2019 (15.x)SQL Server 2019 (15.x), consider the following information.

1.1 SQL Server 2012 安裝程式的規則文件集1.1 Rules Documentation for SQL Server 2012 Setup

問題: SQL Server 安裝程式的作業完成之前會驗證您的電腦組態。Issue: SQL Server Setup validates your computer configuration before the Setup operation completes. SQL Server 安裝程式作業期間執行的各種規則會使用系統組態檢查 (SCC) 報告加以擷取。The various rules that are run during the SQL Server Setup operation are captured using the System Configuration Checker (SCC) report. MSDN Library 上不再提供有關這些安裝程式規則的文件集。The documentation about these setup rules is no longer available on the MSDN library.

因應措施: 您可以參考系統組態檢查報告,深入了解這些安裝程式規則。Workaround : You can refer to the system configuration check report to learn more about these setup rules. 系統組態檢查會產生報告,其中包含每個已執行之規則以及執行狀態的簡短描述。The system configuration check generates a report that contains a short description for each executed rule, and the execution status. 系統組態檢查報告位於 %programfiles%\Microsoft SQL Server\110\Setup Bootstrap\Log\<YYYYMMDD_HHMM>\。The system configuration check report is located at %programfiles%\Microsoft SQL Server\110\Setup Bootstrap\Log\<YYYYMMDD_HHMM>\.

1.2 加入 Distributed Replay Controller 服務的本機使用者帳戶可能會非預期地終止安裝程式1.2 Adding a Local User Account for the Distributed Replay Controller Service Might Terminate Setup Unexpectedly

問題: 在 SQL Server 安裝程式的 [Distributed Replay Controller] 頁面中,當您嘗試加入 Distributed Replay Controller 服務的本機使用者帳戶時,安裝程式將會非預期地終止並顯示「SQL Server 安裝程式失敗」錯誤訊息。Issue: In the Distributed Replay Controller page of SQL Server setup, when attempting to add a local user account for the Distributed Replay Controller service, setup will be terminated unexpectedly with a "SQL Server Setup failure" error message.

因應措施: 在安裝 SQL 期間,請勿經由 [新增目前使用者] 或 [新增...] 來新增本機使用者帳戶。Workaround: During SQL setup, do not add local user accounts via either "Add Current User" or "Add...". 請在安裝之後,依照下列步驟手動加入本機使用者帳戶:After setup, add a local user account manually by using the following steps:

  1. 停止 SQL Server Distributed Replay Controller 服務。Stop the SQL Server Distributed Replay controller service

  2. 在安裝控制器服務的控制器電腦上,於命令提示字元中輸入 dcomcnfg。On the controller computer on which the controller service is installed, from the command prompt, type dcomcnfg.

  3. 在 [元件服務] 視窗中,導覽至 [主控台根目錄] -> [元件服務] -> [電腦] -> [我的電腦] -> [Dconfig] ->[DReplayController] 。In the Component Services window, navigate to Console Root -> Component Services -> Computers -> My Computer -> Dconfig ->DReplayController.

  4. 以滑鼠右鍵按一下 [DReplayController] ,然後按一下 [內容] 。Right-click DReplayController, and then click Properties.

  5. 在 [DReplayController 內容] 視窗的 [安全性] 索引標籤上,按一下 [啟動和啟用權限] 區段中的 [編輯] 。In the DReplayController Properties window, on the Security tab, click Edit in the Launch and Activation Permissions section.

  6. 將 [本機和遠端啟用] 權限授與本機使用者帳戶,然後按一下 [確定] 。Grant the local user account Local and Remote activation permissions, and then click OK.

  7. 按一下 [存取權限] 區段中的 [編輯] 將 [本機和遠端存取] 權限授與本機使用者帳戶,然後按一下 [確定] 。In the Access Permissions section, click Edit and grant the local user account Local and Remote access permissions, and then click OK.

  8. 按一下 [確定] 關閉 [DReplayController 內容] 視窗。Click OK to close the DReplayController Properties window.

  9. 在控制器電腦上,將本機使用者帳戶加入至 [Distributed COM Users] 群組。On the controller computer, add the local user account to the Distributed COM Users group.

  10. 啟動 SQL Server Distributed Replay Controller 服務。Start the SQL Server Distributed Replay controller service.

1.3 SQL Server 安裝程式可能會在嘗試啟動 SQL Server Browser 服務時失敗1.3 SQL Server Setup might fail while trying to start the SQL Server Browser service

問題: SQL Server 安裝程式可能會在嘗試啟動 SQL Server Browser 服務時失敗,並出現類似以下的錯誤:Issue: SQL Server Setup might fail while trying to start the SQL Server Browser service, with errors similar to the following:

The following error has occurred:  
Service 'SQLBrowser' start request failed. Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

中的多個or

The following error has occurred:  
SQL Server Browser configuration for feature 'SQL_Browser_Redist_SqlBrowser_Cpu32' was cancelled by user after a previous installation failure. The last attempted step: Starting the SQL Server Browser service 'SQLBrowser', and waiting for up to '900' seconds for the process to complete.

因應措施: SQL Server 引擎或 Analysis Services 無法安裝時,就可能發生這種情況。Workaround: This can happen when SQL Server Engine or Analysis Services fails to install. 若要修正此問題,請參閱 SQL Server 安裝程式記錄檔,然後疑難排解 SQL Server 引擎和 Analysis Services 失敗。To fix this issue, refer the SQL Server Setup logs, and troubleshoot the SQL Server Engine and Analysis Services failures. 如需詳細資訊,請參閱<檢視與讀取 SQL Server 安裝程式記錄檔>。For more information, see View and Read SQL Server Setup Log Files. 如需詳細資訊,請參閱< View and Read SQL Server Setup Log Files>。For more information, see View and Read SQL Server Setup Log Files.

1.4 在重新命名網路名稱之後,SQL Server 2008、2008 R2 Analysis Services 容錯移轉叢集升級到 SQL Server 2012 可能會失敗1.4 SQL Server 2008, 2008 R2 Analysis Services Failover Cluster upgrade to SQL Server 2012 might fail after renaming the network name

問題: 在您使用 Windows 叢集系統管理員工具變更 Microsoft SQL Server 2008 或 2008 R2 Analysis Services 容錯移轉叢集執行個體的網路名稱之後,升級作業可能會失敗。Issue: After you change the network name of a Microsoft SQL Server 2008, or 2008 R2 Analysis Services failover cluster instance using the Windows Cluster Administrator tool, the upgrade operation might fail.

因應措施: 若要解決這個問題,請根據這篇知識庫文章中解決方法章節的指示來更新 ClusterName 登錄項目。Workaround: To resolve this issue update the ClusterName registry entry following the instructions in the resolution section of this KB article.

1.5 在 Windows Server 2008 R2 Server Core Service Pack 1 上安裝 SQL Server 20121.5 Installing SQL Server 2012 on Windows Server 2008 R2 Server Core Service Pack 1

您可以在 Windows Server 2008 R2 Server Core SP1 上安裝 SQL Server,但有以下限制:You can install SQL Server on Windows Server 2008 R2 Server Core SP1, with the following limitations:

  • Microsoft SQL Server 2012 不支援在 Server Core 作業系統上使用安裝精靈進行安裝。Microsoft SQL Server 2012 does not support Setup using the installation wizard on the Server Core operating system. 在 Server Core 上安裝時,SQL Server 安裝程式支援使用 /Q 參數的完整無訊息模式或使用 /QS 參數的簡單無訊息模式。When installing on Server Core, SQL Server Setup supports full quiet mode by using the /Q parameter, or Quiet Simple mode by using the /QS parameter.

  • 在執行 Windows Server 2008 R2 Server Core SP1 的電腦上,不支援將舊版 SQL Server 升級為 Microsoft SQL Server 2012。Upgrade of an earlier version of SQL Server to Microsoft SQL Server 2012 is not supported on a computer that is running Windows Server 2008 R2 Server Core SP1.

  • 不支援在執行 Windows Server 2008 R2 Server Core SP1 的電腦上安裝 32 位元版 Microsoft SQL Server 2012。Installing a 32-bit version of Microsoft SQL Server 2012 edition is not supported on a computer running Windows Server 2008 R2 Server Core SP1.

  • 在執行 Windows Server 2008 R2 Server Core SP1 的電腦上,Microsoft SQL Server 2012 無法與舊版 SQL Server 並存安裝。Microsoft SQL Server 2012 cannot be installed side-by-side with earlier versions of SQL Server on a computer that is running Windows Server 2008 R2 Server Core SP1.

  • 並非所有 SQL Server 2012 功能都可在 Server Core 作業系統上受到支援。Not all features of SQL Server 2012 are supported on the Server Core operating system. 如需有關支援的功能以及在 Server Core 上安裝 SQL Server 2012 的詳細資訊,請參閱 在 Server Core 上安裝 SQL Server 2012For more information on features supported, and on installing SQL Server 2012 on Server Core, see Install SQL Server 2012 on Server Core.

1.6 語意搜尋需要您安裝其他相依關係1.6 Semantic Search Requires You to Install an Additional Dependency

問題: 統計語意搜尋有其他必要條件,即語意語言統計資料庫,不是由 SQL Server 安裝程式進行安裝。Issue: Statistical Semantic Search has an additional prerequisite, the semantic language statistics database, which is not installed by the SQL Server Setup program.

因應措施: 若要將語意語言統計資料庫設定為語意索引的必要元件,請執行下列工作:Workaround: To set up the semantic language statistics database as a prerequisite for semantic indexing, perform the following tasks:

  1. 在 SQL Server 安裝媒體上,找到並執行名稱為 SemanticLanguageDatabase.msi 的 Windows Installer 套件,以擷取資料庫。Locate and run the Windows Installer package named SemanticLanguageDatabase.msi on the SQL Server installation media to extract the database. 若為 SQL Server 2012 Express,請從 Microsoft 下載中心 (https://www.microsoft.com/download/details.aspx?id=35582) 下載語意語言統計資料庫,然後執行 Windows Installer 套件。For SQL Server 2012 Express, download the semantic language statistics database from Microsoft Download Center (https://www.microsoft.com/download/details.aspx?id=35582), and then run the Windows Installer package.

  2. 將資料庫移至適當的資料夾。Move the database to an appropriate data folder. 若將資料庫保留在預設位置,則必須要變更權限,才能順利地進行附加。If you leave the database in the default location, you must change permissions before you can attach it successfully.

  3. 附加已擷取的資料庫。Attach the extracted database.

  4. 呼叫 sp_fulltext_semantic_register_language_statistics_db 預存程序註冊資料庫,並在附加資料庫時提供您為資料庫命名的名稱。Register the database by calling the stored procedure sp_fulltext_semantic_register_language_statistics_db and providing the name that you gave to the database when you attached it.

若未完成這些工作,則在您嘗試建立語意索引時,將會看到以下的錯誤訊息。If these tasks are not completed, you will see the following error message when you try to create a semantic index.

Msg 41209, Level 16, State 3, Line 1  
A semantic language statistics database is not registered. Full-text indexes using 'STATISTICAL_SEMANTICS' cannot be created or populated.

1.7 在安裝 SQL Server 2012 期間處理安裝必要條件1.7 Installation Prerequisite Handling During SQL Server 2012 Setup

下列項目描述在安裝 SQL Server 2012 期間必要的安裝行為:The following items describe the prerequisite installation behavior during SQL Server 2012 Setup:

  • 只支援在 Windows 7 SP1 或 Windows Server 2008 R2 SP1 上安裝 SQL Server 2012,Installing SQL Server 2012 is supported only on Windows 7 SP1 or Windows Server 2008 R2 SP1. 但在 Windows 7 或 Windows Server 2008 R2 上,安裝程式不會封鎖安裝 SQL Server 2012。However, Setup does not block installing SQL Server 2012 on Windows 7 or Windows Server 2008 R2.

  • 當您選取 Database Engine、Replication、Master Data Services、Reporting Services、Data Quality Services (DQS) 或 SQL Server Management Studio 時,.NET Framework 3.5 SP1 是 SQL Server 2012 的必要條件,但是 SQL Server 安裝程式已不再安裝 Framework。The .NET Framework 3.5 SP1 is a requirement for SQL Server 2012 when you select Database Engine, Replication, Master Data Services, Reporting Services, Data Quality Services (DQS), or SQL Server Management Studio, and the framework is no longer installed by SQL Server Setup.

    • 如果您在 Windows Vista SP2 或 Windows Server 2008 SP2 作業系統電腦上執行安裝程式,且未安裝 .NET Framework 3.5 SP1,SQL Server 安裝程式會要求您下載及安裝 .NET Framework 3.5 SP1,再繼續進行 SQL Server 安裝。If you run Setup on a computer with either the Windows Vista SP2 or Windows Server 2008 SP2 operating system and you do not have the .NET Framework 3.5 SP1 installed, SQL Server Setup requires you to download and install the .NET Framework 3.5 SP1 before you can continue with the SQL Server installation. 您可以從 Windows Update 下載 .NET Framework 3.5 SP1,也可以直接從 這裡下載。You can download the .NET Framework 3.5 SP1 from Windows Update or directly from here. 若要避免安裝 SQL Server 期間中斷,您可以先下載及安裝 .NET Framework 3.5 SP1,再執行 SQL Server 安裝程式。To avoid interruption during SQL Server Setup, download and install the .NET Framework 3.5 SP1 before you run SQL Server Setup.

    • 如果您在 Windows 7 SP1 或 Windows Server 2008 R2 SP1 作業系統電腦上執行安裝程式,您必須啟用 .NET Framework 3.5 SP1,再安裝 SQL Server 2012。If you run Setup on a computer with either the Windows 7 SP1 or Windows Server 2008 R2 SP1 operating system, you must enable the .NET Framework 3.5 SP1 before you install SQL Server 2012.

      使用下列其中一種方法,在 Windows Server 2008 R2 SP1 上啟用 .NET Framework 3.5 SP1:Use one of the following methods to enable .NET Framework 3.5 SP1 on Windows Server 2008 R2 SP1:

      方法 1:使用 [伺服器管理員]Method 1: Use Server Manager

      1. 在 [伺服器管理員] 中,按一下 [加入功能] 顯示可能的功能清單。In Server Manager, click Add Features to display a list of possible features.

      2. 在 [選取功能] 介面中,展開 [.NET Framework 3.5.1 功能] 項目。In the Select Features interface, expand the .NET Framework 3.5.1 Features entry.

      3. 展開 [.NET Framework 3.5.1 功能] 之後,您會看見兩個核取方塊。After you expand .NET Framework 3.5.1 Features, you see two check boxes. 一個是 .NET Framework 3.5.1 的核取方塊,另一個則是 WCF 啟動的核取方塊。One check box is for .NET Framework 3.5.1 and other check box is for WCF Activation. 選取 [.NET Framework 3.5.1] ,然後按 [下一步] 。Select .NET Framework 3.5.1, and then click Next. 除非您也安裝了必要的角色服務和功能,否則無法安裝 .NET Framework 3.5.1 功能。You cannot install .NET Framework 3.5.1 features unless the required role services and features are also installed.

      4. 在 [確認安裝選項] 中檢閱選項,然後按一下 [安裝]。In the Confirm Installation Selections, review the selections, and then click Install.

      5. 讓安裝程序完成,然後按一下 [關閉] 。Let the installation process complete, and then click Close.

      方法 2:使用 Windows PowerShellMethod 2: Use Windows PowerShell

      1. 按一下 [開始] | [所有程式] | [附屬應用程式] Click Start | All Programs | Accessories.

      2. 展開 [Windows PowerShell] 以滑鼠右鍵按一下 [Windows PowerShell] ,然後按一下 [以系統管理員身分執行] 。Expand Windows PowerShell, right-click Windows PowerShell, and click Run as administrator. 請在 [使用者帳戶控制] 方塊中按一下 [是] 。Click Yes in the User Account Control box.

      3. 在 PowerShell 命令提示字元中,輸入下列命令,然後在每個命令後面按下 ENTER:At the PowerShell command prompt, type the following commands and press ENTER after each command:

        Import-Module ServerManager  
        Add-WindowsFeature as-net-framework  
        

      使用以下方法,在 Windows 7 SP1 上啟用 .NET Framework 3.5 SP1:Use the following method to enable .NET Framework 3.5 SP1 on Windows 7 SP1:

      1. 按一下 [開始] | [控制台] | [程式] ,然後按一下 [開啟或關閉 Windows 功能] 。Click Start | Control Panel | Programs, and then click Turn Windows features on or off. 如果系統提示需要系統管理員密碼或確認,請輸入密碼或提供確認。If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

      2. 若要啟用 [Microsoft .NET Framework 3.5.1] ,請選取此功能旁的核取方塊。To enable Microsoft .NET Framework 3.5.1, select the check box next to the feature. 若要關閉某項 Windows 功能,請清除核取方塊。To turn a Windows feature off, clear the check box.

      3. 按一下 [確定] 。Click OK.

      使用部署映像服務與管理 (DISM.exe) 來啟用 .NET Framework 3.5 SP1:Use Deployment Image Servicing and Management (DISM.exe) to enable .NET Framework 3.5 SP1:

      您也可以使用部署映像服務與管理 (DISM.exe) 來啟用 .NET Framework 3.5 SP1。You can also enable .NET Framework 3.5 SP1 using Deployment Image Servicing and Management (DISM.exe). 如需有關在線上啟用 Windows 功能的詳細資訊,請參閱 在線上啟用或停用 Windows 功能For more information about enabling windows features online, see Enable or Disable Windows Features Online. 以下是啟用 .NET Framework 3.5 SP1 的指示:The following are the instructions to enable .NET Framework 3.5 SP1:

      1. 在命令提示字元輸入下列命令,列出作業系統中提供的所有功能。At the command prompt, type the following command to list all of the features available in the operating system.

        sm /online /Get-Features  
        
      2. 選擇性:在命令提示字元鍵入下列命令,列出您感興趣的特定功能相關資訊。Optional: At the command prompt, type the following command to list information about the specific feature you are interested in.

        Dism /online /Get-FeatureInfo /FeatureName:NetFx3  
        
      3. 輸入以下命令來啟用 Microsoft .NET Framework 3.5.1。Type the following command to enable a Microsoft .NET Framework 3.5.1.

        Dism /online /Enable-Feature /FeatureName:NetFx3  
        
  • .NET Framework 4 是 SQL Server 2012 的必要條件。The .NET Framework 4 is a requirement for SQL Server 2012 . SQL Server 安裝程式會在功能安裝步驟期間安裝 .NET Framework 4。SQL Server Setup installs the .NET Framework 4 during the feature installation step.

    在 Windows Server 2008 R2 SP1 Server Core 作業系統上安裝時,SQL Server 2012 Express 不會安裝 .NET Framework 4。SQL Server 2012 Express does not install the .NET Framework 4 when installing on the Windows Server 2008 R2 SP1 Server Core operating system. 在安裝 SQL Server 2012 Express (僅資料庫) 時,如果有 .NET Framework 3.5 SP1 就不需要 .NET Framework 4。When installing SQL Server 2012 Express (Database only) .NET Framework 4 is not required if .NET Framework 3.5 SP1 is present. 當 .NET Framework 3.5 SP1 不存在或是安裝 SQL Server 2012 Management Studio Express、SQL Server 2012 Express with Tools 或 SQL Server 2012 Express with Advanced Services 時,您必須先安裝 .NET Framework 4,然後才能在 Windows Server 2008 R2 SP1 Server Core 作業系統上安裝 SQL Server 2012 Express。When .NET Framework 3.5 SP1 is not present or when installing SQL Server 2012 Management Studio Express, SQL Server 2012 Express with Tools, or SQL Server 2012 Express with Advanced Services, you must install the .NET Framework 4 before you install SQL Server2012 Express on a Windows Server 2008 R2 SP1 Server Core operating system.

  • 為確保 Visual Studio 元件可以正確安裝,您需要為 SQL Server 安裝更新。To make sure that the Visual Studio component can be installed correctly, SQL Server requires you to install an update. SQL Server 安裝程式會檢查此更新的狀態,然後需要您下載並安裝更新才可繼續安裝 SQL Server。SQL Server Setup checks for the presence of this update and then requires you to download and install the update before you can continue with the SQL Server installation. 為避免安裝 SQL Server 期間發生中斷,您可以先如下所述下載並安裝更新,然後執行 SQL Server 安裝程式 (或安裝 Windows Update 上所提供的 .NET Framework 3.5 SP1 之所有更新):To avoid the interruption during SQL Server Setup, you can download and install the update as described below before running SQL Server Setup (or you can install all the updates for the .NET Framework 3.5 SP1 that are available on Windows Update):

    • 如果您將 SQL Server 2012 安裝於 Windows Vista SP2 或 Windows Server 2008 SP2 作業系統的電腦上,可以從 這裡取得所需的更新。If you install SQL Server 2012 on a computer with the Windows Vista SP2 or Windows Server 2008 SP2 operating system, you can get the required update from here.

    • 如果您在 Windows 7 SP1 或 Windows Server 2008 R2 SP1 作業系統電腦上安裝 SQL Server 2012,即已在電腦上安裝此更新。If you install SQL Server 2012 on a computer with the Windows 7 SP1 or Windows Server 2008 R2 SP1 operating system, this update is already installed on the computer.

  • Windows PowerShell 2.0 是安裝 SQL Server 2012 Database Engine 元件和 SQL Server Management Studio 的必要條件,但是 SQL Server 安裝程式已不再安裝 Windows PowerShell。Windows PowerShell 2.0 is a prerequisite for installing SQL Server 2012 Database Engine components and SQL Server Management Studio, but Windows PowerShell is no longer installed by SQL Server Setup. 如果您的電腦沒有 PowerShell 2.0,可以遵循 Windows Management Framework 頁面上的指示啟用此元件。If PowerShell 2.0 is not present on your computer, you can enable it by following the instructions on the Windows Management Framework page. 您取得 Windows PowerShell 2.0 的方式取決於您在哪一個作業系統執行:How you get Windows PowerShell 2.0 depends on which operating system you are running:

    • Windows Server 2008 - Windows PowerShell 1.0 是一項功能,而且可以加入。Windows Server 2008 - Windows PowerShell 1.0 is a feature and can be added. 下載及安裝 Windows PowerShell 2.0 版本 (以 OS 修補程式的形式生效)。Windows PowerShell 2.0 versions are downloaded and installed (effectively as an OS Patch).

    • Windows 7/Windows Server 2008 R2 - 預設會安裝 Windows PowerShell 2.0。Windows 7/Windows Server 2008 R2 - Windows PowerShell 2.0 are installed by default.

  • 如果您打算在 SharePoint 環境中使用 SQL Server 2012 功能,則需要 SharePoint Server 2010 Service Pack 1 (SP1) 和 SharePoint 8 月份累計更新。If you plan to use SQL Server 2012 features in a SharePoint environment, then SharePoint Server 2010 Service Pack 1 (SP1) and the SharePoint August Cumulative Update is required. 您必須先安裝 SP1、SharePoint 8 月份累計更新並完整修補伺服器陣列,然後再將 SQL Server 2012 功能加入至伺服器陣列。You must install SP1, the SharePoint August Cumulative Update, and fully patch the server farm before you add SQL Server 2012 features to the farm. 此需求適用於下列 SQL Server 2012 功能:使用 Database Engine 的執行個體做為伺服器陣列的資料庫伺服器、設定 PowerPivot for SharePoint,或在 SharePoint 模式中部署 Reporting Services。This requirement applies to the following SQL Server 2012 features: using an instance of Database Engine as the farm's database server, configuring PowerPivot for SharePoint, or deploying Reporting Services in SharePoint mode.

1.8 SQL Server 2012 支援的作業系統1.8 Supported Operating Systems for SQL Server 2012

Windows Vista SP2、Windows Server 2008 SP2、Windows 2008 R2 SP1 和 Windows 7 SP1 作業系統都支援 SQL Server 2012。SQL Server 2012 is supported on the Windows Vista SP2, Windows Server 2008 SP2, Windows 2008 R2 SP1, and Windows 7 SP1 operating systems.

1.9 Sync Framework 未包含在安裝套件中1.9 Sync Framework Is Not Included in the Installation Package

問題: Sync Framework 未包含在 SQL Server 2012 安裝套件中。Issue: Sync Framework is not included in the SQL Server 2012 installation package.

因應措施:這個 Microsoft 下載中心頁面下載適當的 Sync Framework 版本。Workaround: Download the appropriate version of Sync Framework from this Microsoft Download Center page.

1.10 如果您解除安裝 Visual Studio 2010 Service Pack 1,就必須修復 SQL Server 2012 執行個體才能還原特定元件1.10 If Visual Studio 2010 Service Pack 1 is uninstalled, the SQL Server 2012 instance must be repaired to restore certain components

問題SQL Server 2012 (11.x)SQL Server 2012 (11.x) 安裝相依於 Visual Studio 2010 Service Pack 1 的某些元件。Issue:SQL Server 2012 (11.x)SQL Server 2012 (11.x) installation is dependent on some components of the Visual Studio 2010 Service Pack 1. 如果您解除安裝 Service Pack 1,某些共用元件就會降級為其原始版本,而且系統會從電腦中完全移除幾個其他元件。If you uninstall Service Pack 1, some of the shared components are downgraded to their original versions, and a few other components are completely removed from the machine.

因應措施: 從原始來源媒體或網路安裝位置修復 SQL Server 2012 (11.x)SQL Server 2012 (11.x) 的執行個體。Workaround: Repair the instance of SQL Server 2012 (11.x)SQL Server 2012 (11.x) from the original source media or network installation location.

  1. 從 SQL Server 安裝媒體啟動 SQL Server 安裝程式 (setup.exe)。Launch the SQL Server Setup program (setup.exe) from SQL Server installation media.

  2. 驗證必要元件和系統之後,安裝程式將會顯示 [SQL Server 安裝中心] 頁面。After prerequisites and system verification, the Setup program will display the SQL Server Installation Center page.

  3. 按一下左側導覽區域中的 [維護] ,然後按一下 [修復] 啟動修復作業。Click Maintenance in the left-hand navigation area, and then click Repair to start the repair operation. 如果使用 [開始] 功能表啟動安裝中心,您將需要在這個階段提供安裝媒體的位置。If the Installation Center was launched using the Start menu, you will need to provide the location of the installation media at this time.

  4. 安裝程式支援規則和檔案常式將會執行,以便確保您的系統已安裝必要元件而且電腦通過安裝程式驗證規則。Setup support rule and file routines will run to ensure that your system has prerequisites installed and that the computer passes Setup validation rules. 按一下 [確定][安裝] 繼續進行。Click OK or Install to continue.

  5. 在 [選取執行個體] 頁面上,選取要修復的執行個體,然後按一下 [下一步] 繼續進行。On the Select Instance page, select the instance to repair, and then click Next to continue.

  6. 修復規則將會執行,以便驗證作業。The repair rules will run to validate the operation. 若要繼續進行,請按 [下一步]To continue, click Next.

  7. [已完成修復準備工作] 頁面會指出作業準備繼續進行。The Ready to Repair page indicates that the operation is ready to proceed. 若要繼續,請按一下 [修復] 。To continue, click Repair.

  8. [修復進度] 頁面會顯示修復作業的狀態。The Repair Progress page shows the status of the repair operation. [完成] 頁面會指出作業已完成。The Complete page indicates that the operation is finished.

如需有關如何修復 SQL Server 執行個體的詳細資訊,請參閱 修復失敗的 SQL Server 2012 安裝For more information on how to repair an instance of SQL Server, see Repair a Failed SQL Server 2012 Installation.

1.11 SQL Server 2012 的執行個體可能會在作業系統升級之後失敗1.11 An instance of SQL Server 2012 might fail after an OS upgrade

問題: 當您將作業系統從 Windows Vista 升級為 Windows 7 SP1 之後,SQL Server 2012 的執行個體可能會失敗並出現下列錯誤。Issue: An instance of SQL Server 2012 might fail with the following error after you upgrade the operating system to Windows 7 SP1 from Windows Vista.

Setup has detected that the .NET Framework version 4 needs to be repaired. Do not restart your computer until Setup is complete.

因應措施:在您升級作業系統之後,請修復 .NET Framework 4 的安裝。Workaround: Repair your installation of the .NET Framework 4 after you upgrade your operating system. 如需詳細資訊,請參閱 如何修復現有的 .NET Framework 安裝For more information, see How to repair an existing installation of the.NET Framework.

1.12 SQL Server 版本升級需要重新啟動1.12 SQL Server Edition upgrade requires a restart

問題:在您升級 SQL Server 2012 執行個體的版本後,與新版本相關聯的某些功能可能無法立即啟動。Issue: When you edition upgrade an instance of SQL Server 2012, some of the functionalities associated with the new edition might not be activated immediately.

因應措施:在 SQL Server 2012 執行個體的版本升級完成之後重新啟動電腦。Workaround: Restart the machine after the edition upgrade of an instance of SQL Server 2012. 如需有關 SQL Server 2012 支援之升級方式的詳細資訊,請參閱 支援的版本與版本升級For more information about supported upgrades in SQL Server 2012, see Supported Version and Edition Upgrades.

1.13 無法升級具有唯讀檔案群組或檔案的資料庫1.13 Database with read-only filegroup or files cannot be upgraded

問題:如果資料庫或其檔案/檔案群組設定為唯讀,您就無法透過附加資料庫或從備份還原資料庫,升級資料庫。Issue: You cannot upgrade a database by either attaching the database or restoring the database from backup if the database or its files/filegroups are set to read-only. 此時,系統會傳回錯誤 3415。Error 3415 is returned. 當您執行 SQL Server 執行個體的就地升級時,也會發生這個問題。This issue also applies when performing an in-place upgrade of an instance of SQL Server. 也就是說,您嘗試透過安裝 SQL Server 2012 來取代現有的 SQL Server 執行個體,而且一個或多個現有的資料庫設定為唯讀。That is, you attempt to replace an existing instance of SQL Server by installing SQL Server 2012 and one or more of the existing databases is set to read-only.

因應措施: 升級之前,請確定資料庫及其檔案/檔案群組設定為可讀寫。Workaround: Before upgrading, ensure that the database and its files/filegroups are set to read-write.

1.14 如果您使用相同的 IP 位址,重新安裝 SQL Server 容錯移轉叢集的執行個體會失敗1.14 Reinstalling an instance of SQL Server Failover Custer fails if you use the same IP address

問題: 若在安裝 SQL Server 容錯移轉叢集執行個體時指定了不正確的 IP 位址,安裝就會失敗。Issue: If you specify an incorrect IP address during an installation of a SQL Server Failover Cluster instance, the installation fails. 解除安裝失敗的執行個體之後,如果您嘗試使用相同的執行個體名稱和正確的 IP 位址來重新安裝 SQL Server 容錯移轉叢集執行個體,安裝仍會失敗。After you uninstall the failed instance, and if you try to reinstall the SQL Server failover cluster instance with the same instance name, and correct IP address, the installation fails. 發生失敗的原因是先前的安裝遺留了重複的資源群組。The failure is because of the duplicate resource group left behind by the previous installation.

因應措施: 若要解決此問題,請在重新安裝時使用不同的執行個體名稱,或在重新安裝之前手動刪除資源群組。Workaround: To resolve this issue, use a different instance name during the reinstallation, or manually delete the resource group before reinstalling. 如需詳細資訊,請參閱 在 SQL Server 容錯移轉叢集中加入或移除節點For more information, see Add or Remove Nodes in a SQL Server Failover Cluster.

horizontal_barhorizontal_bar

2.0 Analysis Services2.0 Analysis Services

2.1 SQL 編輯器和 AS 編輯器無法在相同 SSMS 執行個體中連接到其各自的伺服器執行個體2.1 SQL editor and AS editor cannot connect to their respective server instances in the same SSMS instance

問題: 當 SQL 編輯器已連線時,無法使用 MDX/DMX 編輯器連線到 Analysis Services 伺服器。Issue: Cannot connect to an Analysis Services server using the MDX/DMX editor when the SQL editor is already connected.

使用 SQL Server Management Studio 2012 (SSMS) 時,如果 .sql 檔案已在編輯器中開啟而且連接到 SQL Server 執行個體,則相同 SSMS 執行個體中開啟的 MDX 或 DMX 檔案就無法連接到 AS 伺服器執行個體。When using SQL Server Management Studio 2012 (SSMS), if a .sql file is open in the editor and is connected to a SQL Server instance, an MDX or DMX file when opened in the same instance of SSMS cannot connect to an instance of AS server. 同樣地,如果 MDX 或 DMX 檔案已在 SSMS 的編輯器中開啟,並連接到 AS 伺服器執行個體,則相同 SSMS 執行個體中開啟的 .sql 檔案就無法連接到 SQL Server 執行個體。Likewise, if an MDX or DMX file is already open in the editor in SSMS and connected to an AS server instance, a .sql file when opened in the same instance of SSMS cannot connect to an instance of SQL Server.

因應措施:若要解決此問題,請使用下列任一選項。Workaround: Use one of the following options to resolve this issue.

  • 啟動另一個 SSMS 執行個體,開啟 MDX / DMX 檔案。Start another instance of SSMS to open the MDX / DMX file.

  • 中斷連接 SQL 編輯器,然後將 MDX / DMX 編輯器連接到 AS 伺服器。Disconnect the SQL editor and then connect the MDX / DMX editor to an AS server.

2.2 無法解析 BUILTIN\Administrators 群組名稱時,無法建立或開啟表格式專案2.2 Cannot Create or Open Tabular Projects When BUILTIN\Administrators Group Name Cannot Be Resolved

問題: 您必須是工作空間資料庫伺服器上的系統管理員,才能建立或開啟表格式專案。Issue: You must be an administrator on a workspace database server before you can create or open tabular projects. 您可以透過新增使用者名稱或群組名稱,將使用者新增至伺服器系統管理員群組。A user can be added to the server administrators group by adding the user name or group name. 如果您是 BUILTIN\Administrator 群組的成員,就不能建立或編輯 BIM 檔案,除非工作空間資料庫伺服器聯結至其原始佈建的網域。If you are a member of the BUILTIN\Administrator group, you cannot create or edit BIM files unless the workspace database server is joined to the domain from which it was originally provisioned. 如果您開啟或建立 BIM 檔案,作業將會失敗並出現下列錯誤訊息:If you open or create the BIM file, it will fail with the following error message:

"The BIM file cannot be opened. The server connected to is not valid. Reason: You are not an administrator of server [server name]."

因應措施:Workarounds:

  • 重新聯結工作空間資料庫伺服器與 SQL Server Data Tools (SSDT) 電腦至網域。Re-join the workspace database server and SQL Server Data Tools (SSDT) computer to the domain.

  • 如果工作空間資料庫伺服器及/或 SSDT 電腦不會隨時聯結網域,請加入個別使用者名稱而不要加入 BUILTIN\Administrators 群組做為工作空間資料庫伺服器上的系統管理員。If the workspace database server and/or SSDT computers are not going to be domain joined at all times, add individual user names instead of the BUILTIN\Administrators group as administrators on the workspace database server.

2.3 AS 表格式模型的 SSIS 元件未如預期運作2.3 SSIS Components for AS Tabular Models Do Not Work as Expected

Analysis Services (AS) 的 SQL Server Integration Services (SSIS) 元件未以預期方式針對表格式模型運作。SQL Server Integration Services (SSIS) components for Analysis Services (AS) do not work as expected for tabular models. 以下是當您嘗試為搭配表格式模型運作而撰寫 SSIS 套件時,可能發生的已知問題。The following are known issues that may occur when you try to write an SSIS package for working with tabular models.

問題: AS 連線管理員無法在與資料來源相同的解決方案中使用表格式模型。Issue: The AS Connection Manager cannot use a tabular model in the same solution as a data source.

因應措施: 您必須明確地連線到 AS 伺服器,再設定 AS 處理工作或 AS 執行 DDL 工作。Workaround: You must explicitly connect to the AS server before configuring the AS Processing Task or the AS Execute DDL Task.

當您使用表格式模型時,AS 處理工作有一些問題存在:There are problems with the AS Processing Task when you work with tabular models:

問題: 您沒有看到資料庫、資料表和資料分割,而是看到 Cube、量值群組和維度。Issue: Instead of databases, tables, and partitions, you see cubes, measure groups, and dimensions. 這是工作的限制。This is a limitation of the task.

因應措施: 您仍然可以使用 Cube/量值群組/維度結構來處理表格式模型。Workaround: You can still process your tabular model using the cube/measure group/dimension structure.

問題: 由表格式模式中執行之 AS 支援的一些處理選項並未在 AS 處理工作中公開,如處理重組。Issue: Some processing options supported by AS running in tabular mode are not exposed in the AS Processing Task, such as Process Defrag.

因應措施: 請改用 Analysis Services 執行 DDL 工作,執行包含 ProcessDefrag 命令的 XMLA 指令碼。Workaround: Use the Analysis Services Execute DDL task instead to execute an XMLA script that contains the ProcessDefrag command.

問題: 工具中有些組態選項不適用。Issue: Some configuration options in the tool are not applicable. 例如,處理資料分割時不應該使用「處理相關物件」,而「平行處理」組態選項則包含無效錯誤訊息,說明標準 SKU 上不支援平行處理。For example, "Process related objects" should not be used when processing partitions, and the "Parallel Processing" configuration option contains an invalid error message stating that parallel processing is not supported on the Standard SKU.

因應措施: NoneWorkaround: None

horizontal_barhorizontal_bar

3.0 線上叢書3.0 Books Online

3.1 在設定為只執行 IPv6 的環境中,SQL Server 的說明檢視器會當機3.1 Help Viewer for SQL Server Crashes in Environments Configured to Run Only IPv6

問題:如果您的環境設定為只執行 IPv6,SQL Server 2012 的說明檢視器會當機,並出現下列錯誤訊息:Issue: If your environment is configured to run only IPv6, the Help Viewer for SQL Server 2012 will crash, and you will be presented with the following error message:

HelpLibAgent.exe has stopped working.

重要

適用於只啟用 IPv6 的所有環境。This applies to all environments running with only IPv6 enabled. IPv4 (以及混合 IPv4 與 IPv6) 啟用的環境不受影響。IPv4 (and IPv4 with IPv6) enabled environments are not impacted.

因應措施:若要避免此問題,請啟用 IPv4,或使用下列步驟加入登錄項目,並建立 ACL 以針對 IPv6 啟用說明檢視器:Workaround: To avoid this issue, enable IPv4, or use the following steps to add a registry entry and create an ACL to enable the Help viewer for IPv6:

  1. 在 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Help\v1.0 底下建立名為 "IPv6" 且具有 "1 (DWORD(32 bit))" 值的登錄機碼。Create a registry key with the name "IPv6" and a value of "1 (DWORD(32 bit))" under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Help\v1.0.

  2. 從管理員 CMD 視窗執行下列命令,為 IPv6 通訊埠設定安全性 ACL:Set the security ACL's for the port for IPv6, executing the following from an admin CMD window:

    netsh http add urlacl url=https://[::1]:47873/help/ sddl=D:(A;;GX;;;WD)  
    

horizontal_barhorizontal_bar

4.0 Data Quality Services4.0 Data Quality Services

4.1 叢集中不支援 DQS4.1 DQS Not Supported in a Cluster

問題: SQL Server 叢集安裝中不支援 DQS。Issue: DQS is not supported in a SQL Server cluster installation. 如果您正在安裝 SQL Server 的叢集執行個體,就不得在 [特徵選取] 頁面上選取 [Data Quality Services] 和 [Data Quality Client] 核取方塊。If you are installing a cluster instance of SQL Server, you must not select the Data Quality Services and Data Quality Client check boxes on the Feature Selection page. 如果您在叢集執行個體安裝期間選取這兩個核取方塊 (而且您藉由執行 DQSInstaller.exe 檔案完成 Data Quality Server 安裝),DQS 將會安裝在這個節點上,但是當您在叢集中加入其他節點時無法在其他節點上使用,因此 DQS 無法在其他節點上運作。If these check boxes are selected during cluster instance installation (and you complete the Data Quality Server installation by running the DQSInstaller.exe file), DQS will be installed on this node, but will not be available on additional nodes when you add more nodes to the cluster, and hence will not work on additional nodes.

因應措施: 安裝 SQL Server 2012 累積更新 1 可解決此問題。Workaround: Install SQL Server 2012 Cumulative Update 1 to resolve this issue. 如需指示,請參閱https://support.microsoft.com/kb/2674817For instructions, see https://support.microsoft.com/kb/2674817.

4.2 若要重新安裝 Data Quality Server,請在解除安裝資料品質伺服器之後刪除 DQS 物件4.2 To Reinstall Data Quality Server, Delete the DQS Objects After Uninstalling Data Quality Server

問題: 如果您解除安裝 Data Quality Server,並不會自 SQL Server 執行個體刪除 DQS 物件 (DQS 資料庫、DQS 登入和 DQS 預存程序)。Issue: If you uninstall the Data Quality Server, the DQS objects (DQS databases, DQS logins, and a DQS stored procedure) are not deleted from the SQL Server instance.

因應措施: 若要在相同電腦的同一個 SQL Server 執行個體中重新安裝 Data Quality Server,您必須從該 SQL Server 執行個體中手動刪除 DQS 物件。Workaround: To reinstall Data Quality Server on the same computer and in the same SQL Server instance, you must manually delete the DQS objects from the SQL Server instance. 此外,您也必須從電腦上的 C:\Program Files\Microsoft SQL Server\MSSQL11.<SQL_Server_Instance>\MSSQL\DATA 資料夾中刪除 DQS 資料庫 (DQS_MAIN、DQS_PROJECTS 和 DQS_STAGING_DATA) 檔案,然後再重新安裝資料品質伺服器。Additionally, you must also delete the DQS databases (DQS_MAIN, DQS_PROJECTS, and DQS_STAGING_DATA) files from the C:\Program Files\Microsoft SQL Server\MSSQL11.<SQL_Server_Instance>\MSSQL\DATA folder on your computer before you reinstall Data Quality Server. 否則,Data Quality Server 安裝會失敗。Otherwise, the Data Quality Server installation fails. 若要保留資料 (如知識庫或資料品質專案),請移動資料庫檔案而不要刪除。Move the database files instead of deleting them if you want to preserve data, such as knowledge bases or data quality projects. 如需有關解除安裝程序完成之後移除 DQS 物件的詳細資訊,請參閱 移除 Data Quality Server 物件For more information about removing DQS objects after the uninstall process is complete, see Remove Data Quality Server Objects.

4.3 指示知識探索已終止或互動式清理活動已延遲4.3 Indication of a Terminated Knowledge Discovery or Interactive Cleansing Activity is Delayed

問題: 如果系統管理員在 [活動監控] 畫面上終止活動,則執行知識探索、網域管理或互動式清理活動的互動式使用者在執行下一項作業之後,才會收到活動已被終止的資訊。Issue: If an administrator terminates an activity in the Activity Monitoring screen, an interactive user who is running the knowledge discovery, domain management, or interactive cleansing activity will not receive any indication that his or her activity was terminated until he or she performs the next operation.

因應措施: NoneWorkaround: None

4.4 取消作業會捨棄多項活動的工作4.4 A Cancel Operation Discards Work from Multiple Activities

問題: 如果您針對執行中的知識探索或網域管理活動按一下 [取消] ,而在該活動執行時,先前已完成其他活動但未執行發行作業,則從上次發行以來所執行的所有活動工作都會被捨棄,而不只是捨棄目前的活動。Issue: If you click Cancel for a running knowledge discovery or domain management activity, and other activities have completed previously without a publish operation being performed while the activity is running, the work from all the activities performed since the last publish will be discarded, not just the current one.

因應措施: 若要避免這種狀況,請發行您需要保存在知識庫中的工作,再啟動新的活動。Workaround: To avoid this, publish work that you need to persist in the knowledge base before starting a new activity.

4.5 控制項無法針對大字型適當縮放4.5 Controls Do Not Scale Properly On Large Font Sizes

問題: 如果您將文字大小變更為 [大 - 150%] (在 Windows Server 2008 或 Windows 7 中),或將 [自訂 DPI 設定] 變更為 200% (在 Windows 7 中),便無法存取 [新增知識庫] 頁面上的 [取消] 和 [建立] 按鈕。Issue: If you change the size of text to "Larger - 150%" (in Windows Server 2008 or Windows 7), or change the Custom DPI setting to 200% (in Windows 7), the Cancel and Create buttons on the New Knowledge Base page are not accessible.

因應措施:若要解決這個問題,請將字型設定為較小的大小。Workaround: To resolve the issue, set the font to a smaller size.

4.6 不支援 800x600 螢幕解析度4.6 Screen Resolution of 800x600 Is Not Supported

問題: 如果螢幕解析度設定為 800x600,Data Quality Client 應用程式不會正確顯示。Issue: The Data Quality Client application does not display correctly if the screen resolution is set to 800x600.

因應措施: 若要解決此問題,請將螢幕解析度設定為較高的值。Workaround: To resolve the issue, set the screen resolution to a higher value.

4.7 將來源資料中的 Bigint 資料行對應至 Decimal 定義域以防止資料遺失4.7 Map Bigint Column in the Source Data to a Decimal Domain to Prevent Data Loss

問題: 如果來源資料中的資料行是 bigint 資料類型,您必須在 DQS 中將該資料行對應至 decimal 資料類型的定義域,而不是 integer 資料類型的定義域。Issue: If a column in your source data is of the bigint data type, you must map the column to a domain of the decimal data type rather than the integer data type in DQS. 這是因為 decimal 資料類型代表比 int 資料類型更大範圍的值,因此可以保存較大的值。This is because the decimal data type represents a larger range of values than the int data type and therefore can hold larger values.

4.8 Integration Services 中的 DQS 清理元件不支援 NVARCHAR(MAX) 和 VARCHAR(MAX) 資料類型4.8 NVARCHAR(MAX) and VARCHAR(MAX) Data Types Are Not Supported in the DQS Cleansing Component in Integration Services

問題: Integration Services 中的 DQS 清理元件不支援 nvarchar(max)varchar(max) 資料類型的資料行。Issue: Data columns of the nvarchar(max) and varchar(max) data types are not supported in the DQS Cleansing component in Integration Services. 因此,這些資料行無法在 DQS 清理轉換編輯器的 [對應] 索引標籤中用於對應,所以無法進行清理。As such, these data columns are unavailable for mapping in the Mapping tab of DQS Cleansing Transformation Editor, and hence cannot be cleansed.

因應措施: 使用 DQS 清理元件來處理這些資料行之前,您必須先使用資料轉換,將它們轉換成 DT_STRDT_WSTR 資料類型。Workaround: Before processing these data columns using the DQS Cleansing component, you must convert them to the DT_STR or DT_WSTR data type using the Data Conversion transform.

4.9 新的 SQL Server 執行個體安裝會覆寫開始功能表上執行 DQSInstaller.exe 的項目4.9 The Item to Run DQSInstaller.exe on the Start Menu Is Overwritten On New SQL Server Instance Installation

問題: 如果您選擇在 SQL Server 執行個體中安裝 Data Quality Services,完成 SQL Server 安裝程式之後,系統會在 [開始] 功能表的 [Data Quality Services] 程式群組底下建立名為 [資料品質伺服器安裝程式] 的項目。Issue: If you choose to install Data Quality Services in a SQL Server instance, an item is created on the Start menu under the Data Quality Services program group called Data Quality Server Installer after you complete the SQL Server setup. 不過,如果您在相同的電腦上安裝多個 SQL Server 執行個體,[開始] 功能表上仍會只有單一 [Data Quality Server 安裝程式] 項目。However, if you install multiple SQL Server instances on the same computer, there is still a single Data Quality Server Installer item on the Start menu. 只要按一下這個項目,就會在最近安裝的 SQL Server 執行個體中執行 DQSInstaller.exe 檔案。Clicking this item runs the DQSInstaller.exe file in the most recent installed SQL Server instance.

4.10 活動監控針對失敗的 Integration Services 清理活動顯示不正確的狀態4.10 Activity Monitoring Displays Incorrect Status for Failed Integration Services Cleansing Activities

即使 Integration Services 清理活動失敗,[活動監控] 畫面仍然會在 [目前狀態] 資料行中不正確地顯示 [成功] 。The Activity Monitoring screen incorrectly displays Succeeded even for failed Integration Services Cleansing activities in the Current Status column.

4.11 結構描述名稱並未顯示成資料表/檢視表名稱的一部分4.11 Schema Name Is Not Displayed As Part of Table/View Name

在 Data Quality Client 的對應階段期間,當您在任何 DQS 活動中選取 SQL Server 資料來源時,就會顯示不含結構描述名稱的資料表和檢視表清單。When selecting a SQL Server data source in any of the DQS activities during the mapping stage in Data Quality Client, the list of tables and views is displayed without the schema name. 因此,如果存在許多名稱相同但結構描述不同的資料表/檢視表,您就只能查看資料預覽,或是選取它們,然後查看要對應的可用欄位,藉以進行區別。Therefore, if there are several tables/views with the same name but different schema, they can be distinguished only by looking at the data preview, or by selecting them, and then looking at the available fields to map.

4.12 如果資料來源對應至包含日期類型之子定義域的複合定義域,清理輸出和匯出就會發生問題4.12 Issue with Cleansing Output and Export If Data Source Is Mapped To a Composite Domain Containing a Child Domain of Date Type

在清理資料品質專案中,如果您將來源資料中的欄位對應至具有日期資料類型之子定義域的複合定義域,清理結果的子定義域輸出就會具有不正確的日期格式,而且匯出至資料庫的作業會失敗。In a cleansing data quality project, if you have mapped a field in your source data with a composite domain that has a child domain of date data type, the child domain output in the cleansing result has incorrect date format, and the export to database operation fails.

4.13 對應至名稱包含 ; (分號) 的 Excel 工作表時發生錯誤4.13 Error When Mapping To An Excel Sheet That Contains a ; (Semicolon) In Its Name

問題: 在 Data Quality Client 中任何 DQS 活動的 [對應] 頁面上,如果您對應至名稱包含 ; (分號) 的來源 Excel 工作表,則在 [對應] 頁面上按 [下一步] 時,就會顯示無法處理的例外狀況訊息。Issue: On the Map page of any DQS activity in Data Quality Client, if you map to the source excel sheet that contains a ; (semicolon) in its name, an unhandled exception message is displayed when you click Next on the Map page.

因應措施: 在包含要對應之來源資料的 Excel 檔案中,移除工作表名稱中的 ; (分號),然後再試一次。Workaround: Remove the ; (semicolon) from the sheet name in the Excel file that contains the source data to be mapped, and try again.

4.14 在清理和比對期間,Excel 中未對應之來源欄位的 Date 或 DateTime 值發生問題4.14 Issue with Date or DateTime Values in Unmapped Source Fields in Excel during Cleansing and Matching

問題:如果您的來源資料是 Excel,而且您尚未對應包含 DateDateTime 資料類型值的來源欄位,則清理和比對活動期間會發生下列狀況:Issue: If your source data is Excel and you have not mapped the source fields containing values of Date or DateTime data type, the following happens during the cleansing and matching activities:

  • 未對應的 Date 值會以 yyyymmdd 格式顯示並匯出。The unmapped Date values are displayed and exported in the yyyymmdd format.

  • 未對應之 DateTime 值的時間值會遺失,而且它們會以 yyyymmdd 格式顯示並匯出。The time value is lost for the unmapped DateTime values, and they are displayed and exported in the yyyymmdd format.

因應措施: 您可以在清理活動的 [管理和檢視結果] 頁面以及比對活動的 [比對] 頁面上,於右下角的窗格中檢視未對應的欄位值。Workaround: You can view the unmapped field values in the right-lower pane on the Manage and view results page in the cleansing activity, and on the Matching page in the matching activity.

4.15 無法從包含超過 255 個資料行的 Excel 檔案 (.xls) 匯入定義域值4.15 Cannot Import Domain Values from an Excel File (.xls) Containing More Than 255 Columns of Data

問題: 如果您將值匯入來自 Excel 97-2003 檔案 (.xls) (包含超過 255 個資料行) 的定義域中,會出現例外狀況訊息,而且匯入會失敗。Issue: If you import values into a domain from an Excel 97-2003 file (.xls) that contains more than 255 columns of data, an exception message appears, and the import fails.

因應措施: 若要修正此問題,您可以進行下列任一作業:Workaround: To fix this issue, you can do one of the following:

  • 將 .xls 檔案另存為 .xlsx 檔案,然後將 .xlsx 檔案的值匯入定義域中。Save the .xls file as .xlsx file, and then import the values from the .xlsx file into a domain.

  • 在 .xls 檔案中,移除超過第 255 個資料行之所有資料行的資料、儲存檔案,然後將 .xls 檔案的值匯入定義域中。Remove data in all the columns beyond column 255 in the .xls file, save the file, and then import the values from the .xls file into a domain.

4.16 dqs_administrator 以外的角色無法使用活動監控功能4.16 Activity Monitoring Feature is Unavailable for Roles Other Than dqs_administrator

活動監控功能只適用於擁有 dqs_administrator 角色的使用者。The Activity Monitoring feature is available only for the users having the dqs_administrator role. 如果您的使用者帳戶具有 dqs_kb_editor 或 dqs_kb_operator 角色,則 Data Quality Client 應用程式中將無法使用活動監控功能。If your user account has the dqs_kb_editor or dqs_kb_operator role, the Activity Monitoring feature will be unavailable in the Data Quality Client application.

4.17 在最近使用的知識庫清單中針對定義域管理開啟知識庫時發生錯誤4.17 Error on Opening a Knowledge Base in the Recent Knowledge Base List for Domain Management

問題如果您在 Data Quality Client 首頁畫面中,於 [最近使用的知識庫] 清單中針對定義域管理活動開啟知識庫,您可能會收到以下錯誤:Issue: You might receive the following error if you open a knowledge base in the Recent Knowledge Base list for the domain management activity in the Data Quality Client home screen:

"A configuration with name 'RecentList:KB:<domain>\<username>' already exists in the database."

發生此錯誤是因為 DQS 在 SQL Server 資料庫中與在 C# 中比較字串的方式不同。This occurs because of the difference in the way DQS compares strings in the SQL Server database and C#. SQL Server 資料庫中的字串比較不區分大小寫,但是在 C# 中則區分大小寫。The string comparison in the SQL Server database is case insensitive whereas it is case sensitive in C#.

我們使用範例來說明。Let us illustrate this with an example. 假設有使用者 Domain\user1。Consider a user, Domain\user1. 此使用者使用 "user1" 帳戶登入 Data Quality Client 電腦,並處理知識庫。The user logs on to the Data Quality Client computer using the "user1" account, and works on a knowledge base. DQS 會針對每一位使用者將最近使用的知識庫儲存為 DQS_MAIN 資料庫中 A_CONFIGURATION 資料表內的記錄。DQS stores the recent knowledge base for each user as a record in the A_CONFIGURATION table in the DQS_MAIN database. 在此情況下,此記錄將會以下列名稱儲存:RecentList:KB:Domain\user1。In this case, the record will be stored with the following name: RecentList:KB:Domain\user1. 之後,使用者以 "User1" 身分 (請注意 U 為大寫) 登入 Data Quality Client 電腦,並嘗試在 [最近使用的知識庫] 清單中針對定義域管理活動開啟此知識庫。Later, the user logs on the Data Quality Client computer as "User1" (note the U in upper case), and tries to open the knowledge base in the Recent Knowledge Base list for the domain management activity. DQS 中的基礎程式碼將會比較兩個字串 RecentList:KB:DOMAIN\user1 和 DOMAIN\User1,而 C# 中會進行區分大小寫的字串比較,因為這兩個字串不相符,所以 DQS 會嘗試在 DQS_MAIN 資料庫的 A_CONFIGURATION 資料表中為使用者 (User1) 插入一筆新的記錄。The underlying code in DQS will compare the two strings, RecentList:KB:DOMAIN\user1 and DOMAIN\User1, and considering the case-sensitive string comparison in C#, the strings won't match and therefore DQS will attempt to insert a new record for the user (User1) in the A_CONFIGURATION table in the DQS_MAIN database. 但是,由於 SQL 資料庫中的字串比較不區分大小寫,所以導致該字串已經存在於 DQS_MAIN 資料庫的 A_CONFIGURATION 資料表中,因此插入作業將會失敗。However, owing to the case-insensitive string comparison in SQL database, the string already exists in the A_CONFIGURATION table in the DQS_MAIN database, and the insert operation will fail.

因應措施: 若要修正此問題,您可以進行下列任一作業:Workaround: To fix this issue, you can do one of the following:

  • 執行下列陳述式來確認是否有重複的項目存在:Verify that duplicate entries exist by running the following statement:

    SELECT * FROM DQS_MAIN.dbo.A_CONFIGURATION WHERE NAME like 'RecentList%'  
    

    接下來,您可以執行以下陳述式,只針對受影響的使用者刪除此記錄,方法是變更 WHERE 子句中的值,以符合受影響的定義域和使用者名稱。Next, you can run the following statement to delete the record just for the affected user by changing the value in the WHERE clause to match the affected domain and user name.

    DELETE DQS_MAIN.dbo.A_Configuration WHERE NAME LIKE 'RecentList%<domain>\<username>'  
    

    另外,您也可以針對 DQS 中的所有使用者移除所有最近項目:Alternatively, you could remove all recent items for all users in DQS:

    DELETE DQS_MAIN.dbo.A_Configuration WHERE NAME LIKE 'RecentList%'  
    
  • 在登入 Data Quality Client 電腦時,使用與上次相同的大小寫來指定您的使用者帳戶。Use same capitalization as the last time to specify your user account while logging on to the Data Quality Client computer.

注意

若要避免此問題,請在登入 Data Quality Client 電腦時,使用一致的大小寫規則來指定您的使用者帳戶。To avoid this issue, use consistent capitalization rules to specify your user account while logging on the Data Quality Client computer.

horizontal_barhorizontal_bar

5.0 Database Engine5.0 Database Engine

5.1 使用 Distributed Replay Controller 和 Distributed Replay Client 功能5.1 Use of Distributed Replay Controller and Distributed Replay Client Features

問題: Windows Server 2008、Windows Server 2008 R2 和 Windows Server 7 的 Server Core SKU 中有提供 Distributed Replay Controller 和 Distributed Replay Client 功能,但是 Server Core SKU 中不支援這兩個功能。Issue: Distributed Replay Controller and Distributed Replay Client features are made available in the Server Core SKU of Windows Server 2008, Windows Server 2008 R2, and Windows Server 7, even though these two features are not supported in the Server Core SKU.

因應措施: 請勿在 Windows Server 2008、Windows Server 2008 R2 和 Windows Server 7 的 Server Core SKU 中安裝或使用這兩個功能。Workaround: Do not install or use these two features in the Server Core SKU of Windows Server 2008, Windows Server 2008 R2, and Windows Server 7.

5.2 SQL Server Management Studio 與 Visual Studio 2010 SP1 相依5.2 SQL Server Management Studio depends on Visual Studio 2010 SP1

問題:SQL Server 2012 Management Studio 有賴於 Visual Studio 2010 SP1 才能正確運作。Issue: SQL Server 2012 Management Studio depends on Visual Studio 2010 SP1 to function correctly. 解除安裝 Visual Studio 2010 SP1 可能會導致 SQL Server Management Studio 中的功能遺失並讓 Management Studio 處於不支援的狀態。Uninstalling Visual Studio 2010 SP1 may cause functionality loss in SQL Server Management Studio and will leave Management Studio in an unsupported state. 在此情況下,可能會看到以下問題:The following issues may be seen in this case:

  • ssms.exe 的命令列參數無法正確運作。Command-line parameters to ssms.exe will not work correctly.

  • 嘗試使用 /? 參數執行 ssms.exe 時,Help information displayed when trying to run ssms.exe with the /? 顯示的說明資訊不正確。switch will be incorrect.

  • 針對在 [Windows 檔案總管] 中按兩下所開啟的每一個檔案,都會啟動新的 SSMS 執行個體來開啟檔案。For every file that is opened by double clicking on it in Windows Explorer, a new instance of SSMS will be launched to open the file.

  • 正常使用者模式下無法偵錯查詢。Queries cannot be debugged in the normal user mode.

因應措施:再次安裝 Visual Studio 2010 SP1,並重新啟動 Management Studio。Workaround: Install Visual Studio 2010 SP1 again and restart Management Studio.

5.3 x64 作業系統需要 64 位元 PowerShell 2.05.3 x64 Operating Systems Require 64-bit PowerShell 2.0

問題: 64 位元作業系統上的 SQL Server 2012 執行個體不支援 32 位元的 Windows PowerShell Extensions for SQL Server 安裝。Issue: 32-bit installations of Windows PowerShell Extensions for SQL Server are not supported for instances of SQL Server 2012 on 64-bit operating systems.

因應措施:Workarounds:

  • 安裝具有 64 位元管理工具和 64 位元 Windows PowerShell Extensions for SQL Server 的 64 位元 SQL Server 2012。Install 64-bit SQL Server 2012 with 64-bit Management Tools and 64-bit Windows PowerShell Extensions for SQL Server.

  • 或從 32 位元 Windows PowerShell 2.0 提示匯入 SQLPS 模組。Or, import the SQLPS Module from a 32-bit Windows PowerShell 2.0 prompt.

5.4 在產生指令碼精靈中導覽時可能會發生錯誤5.4 An Error Might Occur When Navigating in the Generate Script Wizard

問題: 在產生指令碼精靈中,按一下 [儲存或發佈指令碼] 產生指令碼,然後按一下 [選擇選項] 或 [設定指令碼編寫選項] 進行導覽之後,再次按一下 [儲存或發佈指令碼] 可能會產生下列錯誤:Issue: After generating a script in the Generate Script Wizard by clicking Save or Publish Scripts, then navigating by clicking Choose Options or Set Scripting Options, clicking Save or Publish Scripts again might result in the following error:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)  
------------------------------  
ADDITIONAL INFORMATION:  
Invalid object name 'sys.federations'. (Microsoft SQL Server, Error: 208)

因應措施: 關閉 [產生指令碼精靈],並重新開啟。Workaround: Close and reopen the Generate Scripts Wizard.

5.5 新的維護計畫配置與舊版的 SQL Server 工具不相容5.5 New Maintenance Plan Layout Not Compatible with Earlier SQL Server Tools

問題: 當 SQL Server 2012 管理工具用來修改舊版 SQL Server 管理工具 (SQL Server 2008 R2、SQL Server 2008 或 SQL Server 2005) 所建立的現有維護計畫時,會以新格式儲存維護計畫。Issue: When SQL Server 2012 management tools are used to modify an existing maintenance plan created in a previous version of SQL Server management tools (SQL Server 2008 R2, SQL Server 2008, or SQL Server 2005), the maintenance plan is saved in a new format. 舊版 SQL Server 管理工具不支援此新格式。Earlier versions of SQL Server management tools do not support this new format.

因應措施:NoneWorkaround: None

5.6 登入自主資料庫時,Intellisense 有限制5.6 Intellisense Has Limitations When Logged in to a Contained Database

問題當自主使用者登入自主資料庫時,SQL Server Management Studio (SSMS) 和 SQL Server Data Tools (SSDT) 中的 Intellisense 無法如預期般運作。Issue: Intellisense in SQL Server Management Studio (SSMS) and SQL Server Data Tools (SSDT) does not function as expected when contained users are logged in to contained databases. 在這類情況下會看到以下行為:The following behavior is seen in such cases:

  1. 無效物件的底線不會出現。Underlining for invalid objects does not appear.

  2. 自動完成清單不會出現。Auto-complete list does not appear.

  3. 內建函數的工具提示說明無效。Tooltip help for built-in functions does not work.

因應措施:NoneWorkaround: None

5.7 AlwaysOn 可用性群組5.7 AlwaysOn Availability Groups

在您嘗試建立可用性群組之前,請參閱線上叢書中的 AlwaysOn 可用性群組的必要條件、限制和建議 (SQL Server)Before you attempt to create an availability group, see Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server) in Books Online. 如需 AlwaysOn 可用性群組的簡介,請參閱線上叢書中的 AlwaysOn 可用性群組 (SQL Server)For an introduction to AlwaysOn Availability Groups, see AlwaysOn Availability Groups (SQL Server)in Books Online.

5.7.1 AlwaysOn 可用性群組的用戶端連接5.7.1 Client-Connectivity for AlwaysOn Availability Groups

更新日期: 2012 年 8 月 13 日Updated on: August 13, 2012

本節說明 AlwaysOn 可用性群組的驅動程式支援,以及不受支援之驅動程式的因應措施。This section describes driver support for AlwaysOn Availability Groups and workarounds for not supported drivers.

驅動程式支援Driver Support

下表摘要列出 AlwaysOn 可用性群組的驅動程式支援:The following table summarizes driver support for AlwaysOn Availability Groups:

驅動程式Driver 多重子網路容錯移轉Multi-Subnet Failover 應用程式的意圖Application Intent 唯讀路由Read-Only Routing 多重子網路容錯移轉:快速單一子網路端點容錯移轉Multi-Subnet Failover: Faster Single Subnet Endpoint Failover 多重子網路容錯移轉:SQL 叢集執行個體的具名執行個體解析Multi-Subnet Failover: Named Instance Resolution For SQL Clustered Instances
SQL Native Client 11.0 ODBCSQL Native Client 11.0 ODBC Yes Yes Yes Yes Yes
SQL Native Client 11.0 OLEDBSQL Native Client 11.0 OLEDB No Yes Yes No No
具有連接修補程式的 ADO.NET 與 .NET Framework 4.0 &#42;ADO.NET with .NET Framework 4.0 with connectivity patch**&#42;** Yes Yes Yes Yes Yes
具有連接修補程式的 ADO.NET 與 .NET Framework 3.5 SP1 &#42;&#42;ADO.NET with .NET Framework 3.5 SP1 with connectivity patch &#42;&#42; Yes Yes Yes Yes Yes
Microsoft JDBC Driver 4.0 for SQL ServerMicrosoft JDBC driver 4.0 for SQL Server Yes Yes Yes Yes Yes

&#42; 下載 ADO .NET 與 .NET Framework 4.0 的連線修補程式:https://support.microsoft.com/kb/2600211.&#42; Download the connectivity patch for ADO .NET with .NET Framework 4.0: https://support.microsoft.com/kb/2600211.

&#42;&#42; 下載 ADO.NET 與 .NET Framework 3.5 SP1 的連線修補程式:https://support.microsoft.com/kb/2654347.&#42;&#42; Download the connectivity patch for ADO.NET with .NET Framework 3.5 SP1: https://support.microsoft.com/kb/2654347.

MultiSubnetFailover 關鍵字和相關聯的功能MultiSubnetFailover Keyword and Associated Features

MultiSubnetFailover 是新的連接字串關鍵字,可用來加快 SQL Server 2012 中 AlwaysOn 可用性群組和 AlwaysOn 容錯移轉叢集執行個體的容錯移轉速度。MultiSubnetFailover is a new connection string keyword used to enable faster failover with AlwaysOn Availability Groups and AlwaysOn Failover Cluster Instances in SQL Server 2012. 當您在連接字串中設定 MultiSubnetFailover=True 時,就會啟用下列三項子功能:The following three sub-features are enabled when MultiSubnetFailover=True is set in connection string:

  • 將多重子網路快速容錯移轉至 AlwaysOn 可用性群組或容錯移轉叢集執行個體的多重子網路接聽程式。Faster multi-subnet failover to a multi-subnet listener for an AlwaysOn Availability Group or Failover Cluster Instances.

    • 將具名執行個體解析為多重子網路 AlwaysOn 容錯移轉叢集執行個體。Named instance resolution to a multi-subnet AlwaysOn Failover Cluster Instance.
  • 將單一子網路快速容錯移轉至 AlwaysOn 可用性群組或容錯移轉叢集執行個體的單一子網路接聽程式。Faster single subnet failover to a single subnet listener for an AlwaysOn Availability Group or Failover Cluster Instances.

    • 這項功能是在連接至具有單一子網路中單一 IP 的接聽程式時使用。This feature is used when connecting to a listener that has a single IP in a single subnet. 它會執行更積極的 TCP 連接重試,加快單一子網路容錯移轉的速度。This performs more aggressive TCP connection retries to speed up single subnet failovers.
  • 將具名執行個體解析為多重子網路 AlwaysOn 容錯移轉叢集執行個體。Named instance resolution to a multi-subnet AlwaysOn Failover Cluster Instance.

    • 這項功能可針對具有多個子網路端點的 AlwaysOn 容錯移轉叢集執行個體加入具名執行個體解析支援。This is to add named instance resolution support for an AlwaysOn Failover Cluster Instances with multiple subnet endpoints.

NET Framework 3.5 或 OLEDB 不支援 MultiSubnetFailover=TrueMultiSubnetFailover=True Not Supported by NET Framework 3.5 or OLEDB

問題: 如果您的可用性群組或容錯移轉叢集執行個體具有相依於不同子網路中多個 IP 位址的接聽程式名稱 (WSFC 叢集管理員中稱為網路名稱或用戶端存取點),而且您使用 ADO.NET 搭配 .NET Framework 3.5 SP1 或使用 SQL Native Client 11.0 OLEDB,對可用性群組接聽程式的用戶端連線要求中,可能有 50% 會連線逾時。Issue: If your Availability Group or Failover Cluster Instance has a listener name (known as the network name or Client Access Point in the WSFC Cluster Manager) depending on multiple IP addresses from different subnets, and you are using either ADO.NET with .NET Framework 3.5SP1 or SQL Native Client 11.0 OLEDB, potentially, 50% of your client-connection requests to the availability group listener will hit a connection timeout.

因應措施: 建議您執行下列任一項工作。Workarounds: We recommend that you do one of the following tasks.

  • 如果您沒有操作叢集資源的權限,請將連接逾時變更為 30 秒 (此值會產生 20 秒 TCP 逾時期間加上 10 秒緩衝時間)。If do not have the permission to manipulate cluster resources, change your connection timeout to 30 seconds (this value results in a 20-second TCP timeout period plus a 10-second buffer).

    優點:如果發生跨子網路的容錯移轉,用戶端復原時間很短。Pros: If a cross-subnet failover occurs, client recovery time is short.

    缺點:半數的用戶端連線需要 20 秒以上Cons: Half of the client connections will take more than 20 seconds

  • 如果您有操作叢集資源的權限,比較建議的作法是將可用性群組接聽程式的網路名稱設定為 RegisterAllProvidersIP=0。If you have the permission to manipulate cluster resources, the more recommended approach is to set the network name of your availability group listener to RegisterAllProvidersIP=0. 如需詳細資訊,請參閱本節後面的<停用 RegisterAllProvidersIP 和減少 TTL 的範例 PowerShell 指令碼>。For more information, see "Sample PowerShell Script to Disable RegisterAllProvidersIP and Reduce TTL", later in this section.

    優點: 您不需要增加用戶端連線逾時值。Pros: You do not need to increase your client-connection timeout value.

    缺點: 如果是跨子網路的容錯移轉,用戶端復原時間可能是 15 分鐘以上,取決於您的 HostRecordTTL 設定和跨網站 DNS/AD 複寫排程設定。Cons: If a cross-subnet failover occurs, the client recovery time could be 15 minutes or longer, depending on your HostRecordTTL setting and the setting of your cross-site DNS/AD replication schedule.

停用 RegisterAllProvidersIP 和減少 TTL 的範例 PowerShell 指令碼Sample PowerShell Script to Disable RegisterAllProvidersIP and Reduce TTL

下列範例 PowerShell 指令碼示範如何停用 RegisterAllProvidersIP 和減少 TTL。The following sample PowerShell script demonstrates how to disable RegisterAllProvidersIP and reduce TTL. 請使用您要變更的接聽程式名稱來取代 yourListenerNameReplace yourListenerName with the name of the listener you are changing.

Import-Module FailoverClusters  
Get-ClusterResource yourListenerName|Set-ClusterParameter RegisterAllProvidersIP 0  
Get-ClusterResource yourListenerName|Set-ClusterParameter HostRecordTTL 300  

5.7.2 不支援從設定可用性群組的 CTP3 升級5.7.2 Upgrading from CTP3 with availability group configured is not supported

升級之前,請卸除可用性群組,然後重新建立它。Drop the availability group and recreate it before you upgrade. 這種行為是基於 CTP3 組建的限制。This is due to a limitation in the CTP3 build. 未來的組建將沒有這項限制。Future builds will not have this restriction.

5.7.3 如果您的執行個體已經設定可用性群組,就不支援 CTP3 與更新版本的並存安裝5.7.3 Side by Side Installation of CTP3 with later versions is not supported if you have an availability group configured in your instance

這種行為是基於 CTP3 組建的限制。This is due to a limitation in the CTP3 build. 未來的組建將沒有這項限制。Future builds will not have this restriction.

5.7.4 不支援 CTP3 與新版容錯移轉叢集執行個體的並存安裝5.7.4 Side by Side Installation of CTP3 with later versions of Failover Cluster Instances is not supported.

這種行為是基於 CTP3 組建的限制。This is due to a limitation in the CTP3 build. 未來的組建將沒有這項限制。Future builds will not have this restriction. 若要從 CTP3 升級容錯移轉叢集執行個體,請務必同時升級節點上的所有執行個體。To upgrade failover cluster instances from CTP3 make sure to upgrade all instances on a node at the same time.

5.7.5 當您在具有 AlwaysOn 的相同子網路中使用多個 IP 時,可能會發生逾時5.7.5 Timeouts may occur when using multi IPs in the same subnet with AlwaysOn

問題: 當您在具有 AlwaysOn 的相同子網路中使用多個 IP 時,有時客戶可能會看到逾時。Issue: When using multi IPs in the same subnet with AlwaysOn, customers may sometimes see a timeout. 如果清單中的首要 IP 無效,就會發生這個情況。This happens if the top IP in the list is bad.

因應措施: 在連接字串中使用 'multisubnetfailover = true'。Workaround: Use 'multisubnetfailover = true' in the connection string.

5.7.6 由於 Active Directory 配額而無法建立新的可用性群組接聽程式5.7.6 Failure to Create New Availability Group Listeners Because of Active Directory Quotas

問題: 新可用性群組接聽程式的建立作業可能會在建立時失敗,因為您已達到參與叢集節點電腦帳戶的 Active Directory 配額。Issue: The creation of a new availability group listener may fail upon creation because you have reached an Active Directory quota for the participating cluster node machine account. 如需詳細資訊,請參閱 如何排解叢集服務帳戶修改電腦物件時所遇到的疑難Active Directory 配額For more information, see How to troubleshoot the Cluster service account when it modifies computer objects and Active Directory Quotas.,

5.7.7 NetBIOS 發生衝突,因為可用性群組接聽程式的名稱使用完全相同的 15 個字元前置詞5.7.7 NetBIOS Conflicts Because Availability Group Listener Names Use an Identical 15-Character Prefix

如果您有兩個由相同 Active Directory 所控制的 WSFC 叢集,而且嘗試使用超過 15 個字元的名稱以及完全相同的 15 個字元前置詞,在這兩個叢集中建立可用性群組接聽程式,就會收到一則錯誤,指出系統無法讓虛擬網路名稱資源上線。If you have two WSFC clusters that are controlled by the same Active Directory and you try to create availability group listeners in both of clusters using names with more than 15 characters and an identical 15 character prefix, you will get an error reporting that the Virtual Network Name resource could not be brought online. 如需有關 DNS 名稱之前置詞命名規則的詳細資訊,請參閱 指派網域名稱For information about prefix naming rules for DNS names, see Assigning Domain Names

horizontal_barhorizontal_bar

6.0 Integration Services6.0 Integration Services

6.1 Oracle 適用的異動資料擷取服務和異動資料擷取設計工具主控台6.1 The Change Data Capture Service for Oracle and the Change Data Capture Designer Console for Oracle

Oracle CDC 服務是一種 Windows 服務,可掃描 Oracle 交易記錄,並將相關 Oracle 資料表的變更擷取到 SQL Server 變更資料表中。The CDC Service for Oracle is a Windows service that scans Oracle transaction logs and captures changes to Oracle tables of interest into SQL Server change tables. CDC 設計工具主控台是用來開發及維護 Oracle CDC 執行個體。The CDC Designer Console is used to develop and maintain Oracle CDC Instances. CDC 設計工具主控台是一種 Microsoft Management Console (MMC) 嵌入式管理單元。The CDC Designer Console is a Microsoft Management Console (MMC) snap-in.

6.1.1 安裝 Oracle CDC 服務和 Oracle CDC 設計工具6.1.1 Install the CDC Service for Oracle and the CDC Designer for Oracle

問題: SQL Server 安裝程式不會安裝 CDC 服務和 CDC 設計工具。Issue: The CDC Service and CDC Designer are not installed by SQL Server Setup. 您必須依照更新說明檔的描述,在符合需求和必要條件的電腦上手動安裝 CDC 服務或 CDD 設計工具。You must manually install the CDC Service or CDD Designer on a computer that meets the requirements and prerequisites as described in the updated Help files.

因應措施: 若要安裝 Oracle CDC 服務,請從 SQL Server 安裝媒體手動執行 AttunityOracleCdcService.msi。Workaround: To install the CDC Service for Oracle, manually run AttunityOracleCdcService.msi from the SQL Server installation media. 若要安裝 CDC 設計工具主控台,請從 SQL Server 安裝媒體手動執行 AttunityOracleCdcDesigner.msi。To install the CDC Designer Console, manually run AttunityOracleCdcDesigner.msi from the SQL Server installation media. x86 和 x64 的安裝套件位於 SQL Server 安裝媒體的 .\Tools\AttunityCDCOracle\ 中。Installation packages for x86 and x64 are located in .\Tools\AttunityCDCOracle\ on the SQL Server installation media.

6.1.2 F1 說明功能指向不正確的文件檔6.1.2 F1 Help Functionality Points to Incorrect Documentation Files

問題: 當您使用 F1 說明下拉式清單或在 Attunity 主控台中按一下 "?" 時,無法存取正確的說明文件。Issue: You cannot access the correct Help documentation by using either the F1 Help drop-down list or by clicking the "?" in the Attunity Consoles. 這些方法指向不正確的 chm 檔案。These methods point to incorrect chm files.

因應措施: 當安裝 Oracle CDC 服務或 Oracle CDC 設計工具時,便會安裝正確的 chm 檔案。Workaround: The correct chm files are installed when the CDC Service for Oracle and CDC Designer for Oracle are installed. 若要檢視正確的說明內容,請直接從這個位置啟動 chm 檔案: %Program Files%\Change Data Capture for Oracle by Attunity\*.chmTo view the correct Help content, launch the chm files directly from this location: %Program Files%\Change Data Capture for Oracle by Attunity\*.chm.

horizontal_barhorizontal_bar

7.0 Master Data Services7.0 Master Data Services

7.1 修正叢集中的 MDS 安裝7.1 Fixing an MDS installation in a Cluster

問題: 如果您在選取 [Master Data Services] 核取方塊的情況下安裝 RTM 版本的 SQL Server 2012 叢集執行個體,將會在單一節點上安裝 MDS,但是 MDS 將無法在您加入至叢集的其他節點上使用及運作。Issue: If you install a clustered instance of the RTM version of SQL Server 2012 with the Master Data Services checkbox selected, MDS will be installed on a single node, but it will not be available and will not work on additional nodes that you add to the cluster.

因應措施:若要解決此問題,您必須安裝 SQL Server 2012 累積更新 1 (CU1) 並執行下列步驟:Workaround: To resolve this issue, you must install the SQL Server 2012 Cumulative Release 1 (CU1), performing the following steps:

  1. 確定沒有任何現有的 SQL/MDS 安裝。Make sure that there is no existing SQL/MDS installation.

  2. 將 SQL Server 2012 CU1 下載至本機目錄中。Download SQL Server 2012 CU1 into a local directory.

  3. 在主要叢集節點上安裝具有 MDS 功能的 SQL Server 2012,然後在任何其他叢集節點上安裝具有 MDS 功能的 SQL Server 2012。Install SQL Server 2012 with the MDS feature on the primary cluster node, and then install SQL Server 2012 with the MDS feature on any additional cluster nodes.

如需有關這些問題的詳細資訊,以及如何執行上述步驟的詳細資訊,請參閱 https://support.microsoft.com/kb/2683467For more information about the issues, and information about how to perform the above steps, see https://support.microsoft.com/kb/2683467.

7.2 需要 Microsoft Silverlight 57.2 Microsoft Silverlight 5 Required

若要在主資料管理員 Web 應用程式中工作,用戶端電腦必須安裝 Silverlight 5.0。To work in the Master Data Manager web application, Silverlight 5.0 must be installed on the client computer. 如果您沒有必要的 Silverlight 版本,系統將會在您導覽至需要 Silverlight 的 Web 應用程式區域時提示安裝 Silverlight。If you do not have the required version of Silverlight, you will be prompted to install it when you navigate to an area of the web application that requires it. 您可以從 https://go.microsoft.com/fwlink/?LinkId=243096 安裝 Silverlight 5。You can install Silverlight 5 from https://go.microsoft.com/fwlink/?LinkId=243096.

horizontal_barhorizontal_bar

8.0 Reporting Services8.0 Reporting Services

8.1 Reporting Services 與 SQL Server PDW 的連接需要更新的驅動程式8.1 Reporting Services Connectivity to SQL Server PDW Requires Updated Drivers

從 SQL Server 2012 Reporting Services 連接到 Microsoft SQL Server PDW Appliance Update 2 及更新的版本需要 PDW 連接驅動程式的更新。Connectivity from SQL Server 2012 Reporting Services to Microsoft SQL Server PDW Appliance Update 2 and higher requires an update to the PDW connectivity drivers. 如需詳細資訊,SQL Server PDW 客戶應該連絡 Microsoft 支援人員。For more information, SQL Server PDW customers should contact Microsoft support.

horizontal_barhorizontal_bar

9.0 StreamInsight9.0 StreamInsight

SQL Server 2012 包括 StreamInsight 2.0。SQL Server 2012 includes StreamInsight 2.0. StreamInsight 2.0 需要 Microsoft SQL Server 2012 授權和 .NET Framework 4.0。StreamInsight 2.0 requires a Microsoft SQL Server 2012 license and .NET Framework 4.0. 其中包含許多效能改良和幾個錯誤修正。It includes a number of performance improvements along with few bug fixes. 如需詳細資訊,請參閱 Microsoft StreamInsight 2.0 版本資訊For more information see the Microsoft StreamInsight 2.0 Release Notes. 若要個別下載 StreamInsight 2.0,請瀏覽 Microsoft 下載中心的 Microsoft StreamInsight 2.0 下載頁面In order to download StreamInsight 2.0 separately, please visit the Microsoft StreamInsight 2.0 download page on the Microsoft Download Center.

horizontal_barhorizontal_bar

10.0 Upgrade Advisor10.0 Upgrade Advisor

問題當您嘗試在任何支援的中文 (香港) 作業系統 (OS) Windows 版本上安裝升級建議程式時,可能會發現未啟用安裝升級建議程式的連結。Issue: When you try to install Upgrade Advisor on any supported Windows version in Chinese (Hong Kong) operating systems (OS), you might find that the link to install Upgrade Advisor is not enabled.

因應措施:在 SQL Server 2012 媒體中的 \1028_CHT_LP\x64\redist\Upgrade Advisor\1028_CHT_LP\x86\redist\Upgrade Advisor 上找出 SQLUA.msi 檔案,視您的作業系統架構而定。Workaround: Locate the SQLUA.msi file on your SQL Server 2012 media at \1028_CHT_LP\x64\redist\Upgrade Advisor or at \1028_CHT_LP\x86\redist\Upgrade Advisor, depending on your operating system architecture.

horizontal_barhorizontal_bar