Hãy nâng cấp lên Microsoft Edge để tận dụng các tính năng mới nhất, bản cập nhật bảo mật và hỗ trợ kỹ thuật. Show
KB3182545 - SQL Server 2016 Service Pack 1 release information
Trong bài viết nàyRelease Date: November 16, 2016 Version: 13.0.4001.0 This article contains important information to read before you install Microsoft SQL Server 2016 Service Pack 1 (SP1). It describes how to get the service pack, the list of fixes that are included in the service pack, known issues, and a list of copyright attributions for the product. Note This article serves as a single source of information to locate all documentation that's related to this service pack. It includes all the information that you previously found in the release notes and Readme.txt files. Known issues in this service packSQL Server Reporting ServicesAfter you install SQL Server 2016 SP1, you may encounter the following issues when you use SQL Server Reporting Services:
Install the hotfix in KB 3207512 to address these issues. SQL Server Integration Services (SSIS)After you install SQL Server 2016 SP1, the DCOM permissions for launching and accessing Integration Services service are reset to default permissions. If you have customized DCOM permissions, you'll need to reapply the customization. ODBC Driver 13.1With the default installation of SQL Server 2016, ODBC Driver 13.0 is installed on the server which is used by SQL Agent and SSMS (installed on server) to connect to the SQL Server instance. If you have installed ODBC Driver 13.1 on your server for any reason, SQL Server 2016 SP1 installation overrides the ODBC Driver 13.1 installation and the fixes introduced in 13.1 like KB 3185365 may be lost. In this case post installation of SQL Server 2016 SP1, it's recommended to uninstall the ODBC Driver installed by SQL Server 2016 SP1 and install ODBC Driver 13.1. To check for ODBC Driver installed on the server, you can go to Control Panel of the server -> Programs and Features -> Search for ODBC. The version number of ODBC Driver 13.1 is 13.1.811.168 as shown below: List of fixes included in SQL Server 2016 SP1Microsoft SQL Server 2016 service packs are cumulative updates. SQL Server 2016 SP1 upgrades all editions and service levels of SQL Server 2016 to SQL Server 2016 SP1. In addition to the fixes that are listed in this article, SQL Server 2016 SP1 includes hotfixes that were included in SQL Server 2016 Cumulative Update 1 (CU1) to SQL Server 2016 CU3. For more information about the cumulative updates that are available in SQL Server 2016, see SQL Server 2016 build versions. Note
For more information about the bugs that are fixed in SQL Server 2016 SP1, go to the following Microsoft Knowledge Base articles. Bug reference Description An update is available that extends the Trace extended event with security protocol handshake information in SQL Server 2016 (KB3191296) How to use DBCC CLONEDATABASE to generate a schema and statistics-only copy of a user database in SQL Server 2014 SP2 and SQL Server 2016 SP1 (KB3177838) Supports DROP TABLE DDL for articles that are included in transactional replication in SQL Server 2014 or in SQL Server 2016 SP1 (KB3170123) Update to add a memory grant warning to the Showplan XML in SQL Server 2014 or 2016 (KB3172997) Update to add DMF sys.dm_db_incremental_stats_properties in SQL Server 2014 or 2016 (KB3170114) Update to expose maximum memory enabled for a single query in Showplan XML in SQL Server 2014 or 2016 (KB3170112) Information about enabled trace flags is added to the showplan XML in SQL Server 2014 SP2 or 2016 (KB3170115) Improved diagnostics for query execution plans that involve residual predicate pushdown in SQL Server (KB3107397) Update adds AlwaysOn extended events and performance counters in SQL Server 2014 or 2016 (KB3173156) Adds a stored procedure for the manual cleanup of the change tracking side table in SQL Server 2014 SP2 or 2016 SP1 (KB3173157) An update is available that introduces a new query hint USE HINT in SQL Server 2016 (KB3189813) An update to introduce a new Transact-SQL statement CREATE OR ALTER in SQL Server 2016 (KB3190548) Update to improve diagnostics by exposing data type of the parameters for parameterized queries in showplan XML output in SQL Server 2016 (KB3190761) An update is available that adds support for self-referential constraints in the new Referential Integrity Operator in SQL Server 2016 (KB3191273) Update to improve diagnostics for query execution plans that involve residual predicate pushdown in SQL Server 2016 (KB3190762) A new DynamicManagement Function "sys.dm_exec_query_statistics_xml" is available in SQL Server 2016 Service Pack 1 (KB3190871) An update is available that adds overall query execution statistics information to the STATISTICS XML output in SQL Server 2016 (KB3201552) FIX: "'Salt' attribute for Password is missing in the project manifest" error when you close and reopen an SSIS BI project in SQL Server 2016 (KB3189687) FIX: A severe error when you use the sys.dm_db_uncontained_entities DMV in SQL Server 2014 or 2016 (KB3172998) "Log provider "Microsoft.LogProviderSQLServer" is not installed correctly" error when you open the Configure SSIS Logs window (KB3100256) FIX: "Unable to create restore plan due to break in the LSN chain" error when you restore differential backup in SSMS (KB3065060) Error when you execute SSIS package on FIPS-enabled Windows (KB2925865) FIX: Memory grant that's required to run optimized nested loop join isn't reflected in Showplan XML in SQL Server 2014 or 2016 (KB3170116) FIX: SQL Server error log incorrectly mentions logical processors when soft-NUMA is enabled (KB3189663) DMV sys.dm_os_memory_nodes returns a non-zero value for the pages_kb value for the DAC node in SQL Server 2016 (KB3170015) FIX: DBCC CHECKDB or CHECKTABLE returns false positives for data corruption and assertion failures in SQL Server 2014 or 2016 (KB3173766) FIX: Installation of Cumulative Update 1 for SQL Server 2016 fails on a named instance (KB3189709) FIX: Deadlock when you execute a query plan with a nested loop join in batch mode in SQL Server 2014 or 2016 (KB3195825) FIX: Long compilation time for a query that contains many distinct operators in SQL Server 2016 (KB3201554) FIX: FileTable directory stops responding when you create multiple files concurrently in SQL Server 2014 or 2016 (KB3191062) FIX: Queries that use CHANGETABLE use much more CPU in SQL Server 2014 SP1 or in SQL Server 2016 (KB3180060) FIX: SQL Server 2016 doesn't log error messages that have a severity level of 21 for checksum mismatches found in In-Memory OLTP checkpoint files (KB4019715) FIX: SQL Server 2016 stops responding when you restore databases that contain memory-optimized tables (KB3197605) FIX: SQL Server Managed Backup to Windows Azure tries to back up database snapshots in SQL Server (KB3168708) New performance feature that accelerates transaction commit times (latency) by up to 2-4X, when employing Storage Class Memory (NVDIMM-N nonvolatile storage) Poor performance when you run INSERT.. SELECT operations in SQL Server 2016 (KB3180087) "A digitally signed driver is required" warning when you install SQL Server packages in Windows Server 2016 and Windows 10 (KB3203693) FIX: Missing columns aren't specified in the error message when you import data by using the Import and Export Wizard (KB3112704) Additional resolutionsResolutions to the following issues are also included in SQL Server 2016 SP1. Bug reference Description Fix area
NULL values are ignored when altering the data type of a column from text to varchar(max). Engine Sqlcmd quits without error if the query text contains both embedded comments and curly braces For more information about how to upgrade your SQL Server installation to SQL Server 2016 SP1, see Supported version and edition upgrades. How to get SQL Server 2016 SP1SQL Server 2016 SP1 is available for download at the SQL Server 2016 SP1 download page. Note After you install the service pack, the SQL Server service version should be reflected as 13.0.4422.0. Uninstalling SQL Server 2016 SP1 (not recommended)If for any reason you choose to uninstall SQL Server 2016 SP1, the uninstallation of SQL Server 2016 SP1 isn't blocked and you'll be able to uninstall SQL Server 2016 SP1 like any other service pack. However, if you're running Standard, Web, Express edition of SQL Server and leveraging some of the new features which are unlocked only starting SQL Server 2016 SP1, you might see some unforeseen errors or databases might even be left in suspect state after uninstallation of SQL Server 2016 SP1. Even worse would be if the system databases are using new features for example, partitioned table in master database, it can lead to SQL Server instance unable to start after uninstalling SQL Server 2016 SP1. Hence it's recommended to validate all the new features are disabled or dropped before you choose to uninstall SQL Server 2016 SP1 on editions other than Enterprise Edition. It isn't possible to drop memory_optimized_data filegroup. Hence if you have setup `"}")`3 filegroup on your database with SP1, you shouldn't uninstall SQL Server 2016 SP1 in that case else the database will get in suspect mode with following error message logged in the error log: <DateTime> spid15s Error: 41381, Severity: 21, State: 1. <DateTime> spid15s The database cannot be started in this edition of SQL Server because it contains a MEMORY_OPTIMIZED_DATA filegroup. See Books Online for more details on feature support in different SQL Server editions. Copyright attributions
Copyright 2012 Microsoft. All rights reserved. ReferencesFor more information about how to determine the current SQL Server version and edition, select the following article number to go to the article in the Microsoft Knowledge Base: 321185 How to identify your SQL Server version and edition The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. |