![]() Information about enabled trace flags is added to the showplan XML in SQL Server 2014 SP2 or 2016 (KB3170115) Update to expose maximum memory enabled for a single query in Showplan XML in SQL Server 2014 or 2016 (KB3170112) Update to add DMF sys.dm_db_incremental_stats_properties in SQL Server 2014 or 2016 (KB3170114) Update to add a memory grant warning to the Showplan XML in SQL Server 2014 or 2016 (KB3172997) Supports DROP TABLE DDL for articles that are included in transactional replication in SQL Server 2014 or in SQL Server 2016 SP1 (KB3170123) 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) Bug referenceĪn update is available that extends the Trace extended event with security protocol handshake information in SQL Server 2016 (KB3191296) This list will be updated when more articles are released.įor more information about the bugs that are fixed in SQL Server 2016 SP1, go to the following Microsoft Knowledge Base articles.Additional fixes that aren't documented here may also be included in the service pack.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.įor more information about the cumulative updates that are available in SQL Server 2016, see SQL Server 2016 build versions. SQL Server 2016 SP1 upgrades all editions and service levels of SQL Server 2016 to SQL Server 2016 SP1. Microsoft SQL Server 2016 service packs are cumulative updates. List of fixes included in SQL Server 2016 SP1 The version number of ODBC Driver 13.1 is 13.1.811.168 as shown below: To check for ODBC Driver installed on the server, you can go to Control Panel of the server -> Programs and Features -> Search for ODBC. 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. 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. With 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 customized DCOM permissions, you'll need to reapply the customization. SQL Server Integration Services (SSIS)Īfter you install SQL Server 2016 SP1, the DCOM permissions for launching and accessing Integration Services service are reset to default permissions. Install the hotfix in KB 3207512 to address these issues. In certain scenarios, the Print button stops working. If Reporting Services is set to use a secure (https/SSL) connection, a warning about security content may be displayed. Known issues in this service pack SQL Server Reporting ServicesĪfter you install SQL Server 2016 SP1, you may encounter the following issues when you use SQL Server Reporting Services: It includes all the information that you previously found in the release notes and Readme.txt files. This article serves as a single source of information to locate all documentation that's related to this service pack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |