SQL Server 2016 Release Notes

SQL Server 2016 and later
 

Updated: November 28, 2016

This topic describes limitations and issues with SQL Server 2016 .

Try it out:

Download from Evaluation Center Download SQL Server 2016 from the Evaluation Center

Azure Virtual Machine small Have an Azure account? Then go Here to spin up a Virtual Machine with SQL Server 2016 SP1 already installed.

Download SSMS SSMS: To get the latest version of SQL Server Management Studio, see Download SQL Server Management Studio (SSMS).

For information on what's new, see What's New in SQL Server 2016.

info_tip 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.

repl_icon_warn  Install Patch Requirement (GA)

Issue and customer impact: Microsoft has identified a problem that affects the Microsoft VC++ 2013 Runtime binaries that are installed as a prerequisite by SQL Server 2016. An update is available to fix this problem. If this update to the VC runtime binaries is not installed, SQL Server 2016 may experience stability issues in certain scenarios. Before you in stall SQL Server 2016, check to see if the computer needs the patch described in KB 3164398. The patch is also inlcuded in Cumulative Update Package 1 (CU1) for SQL Server 2016 RTM.

Resolution: Do one of the following:

  • Install KB 3138367 - Update for Visual C++ 2013 and Visual C++ Redistributable Package. This is the preferred resolution. You can install this before or after you install SQL Server 2016.

    If SQL Server 2016 is already installed, do the following steps in order:

    1. Download the appropriate vcredist_*exe.
    2. Stop the SQL Server service for all instances of the database engine.
    3. Install KB 3138367.
    4. Reboot the computer.
  • Install KB 3164398 - Critical Update for SQL Server 2016 MSVCRT prerequisites.

    If you use KB 3164398, you can install during SQL Server installation, through Microsoft Update, or from Microsoft Download Center.

    • During SQL Server 2016 Installation: If the computer running SQL Server setup has internet access, SQL Server setup will check for the update as part of the overall SQL Server installation. If you accept the update, setup will download and update the binaries during installation.

    • Microsoft Update: The update is available from Microsoft Update as a critical non-security SQL Server 2016 update. Installing through Microsoft update, after SQL Server 2016 will require the server to be restarted following the update.

    • Download Center: Finally, the update is available from the Microsoft Download Center. You can download the software for the update and install it on servers after they have SQL Server 2016.

Stretch Database

Problem with a specific character in a database or table name

Issue and customer impact: Attempting to enable Stretch Database on a database or a table fails with an error if the name of the object includes a character that's treated as a different character when converted from lower case to upper case. An example of a character that causes this issue is the character "ƒ" (created by typing ALT+159) .

Workaround: If you want to enable Stretch Database on the database or the table, the only option is to rename the object and remove the problem character.

Problem with an index that uses the INCLUDE keyword

Issue and customer impact: Attempting to enable Stretch Database on a table that has an index that uses the INCLUDE keyword to include additional columns in the index fails with an error.

Workaround: Drop the index that uses the INCLUDE keyword, enable Stretch Database on the table, then recreate the index. If you do this, be sure to follow your organization's maintenance practices and policies to ensure minimal or no impact to users of the affected table.

Query Store

Problem with automatic data cleanup on editions other than Enterprise and Developer

Issue and customer impact: Automatic data cleanup fails on editions other than Enterprise and Developer. Consequently, space used by the Query Store will grow over time until configured limit is reached, if data is not purged manually. If not mitigated, this issue will also fill up disk space allocated for the error logs, as every attempt to execute cleanup will produce a dump file. Cleanup activation period depends on the workload frequency, but it is no longer than 15 min.

Workaround: If you plan to use Query Store on editions other than Enterprise and Developer, you need to explicitly turn off cleanup policies. It can be done either from SQL Server Management Studio (Database Properties page) or via Transact-SQL script:

ALTER DATABASE <database name> SET QUERY_STORE (OPERATION_MODE = READ_WRITE, CLEANUP_POLICY = (STALE_QUERY_THRESHOLD_DAYS = 0), SIZE_BASED_CLEANUP_MODE = OFF)

Additionally, consider manual cleanup options to prevent Query Store from transitioning to read-only mode. For example, run the following query to periodically clean entire data space:

ALTER DATABASE <database name> SET QUERY_STORE CLEAR

Also, execute the following Query Store stored procedures periodically to clean runtime statistics, specific queries or plans:

  • sp_query_store_reset_exec_stats

  • sp_query_store_remove_plan

  • sp_query_store_remove_query

Product Documentation (GA)

Issue and customer impact: A downloadable version of the SQL Server 2016 documentation is not yet available. When you use Help Library Manager to attempt to Install content from online, you will see the SQL Server 2012 and SQL Sever 2014 documentation but there are no options for SQL Server 2016 documentation.

Workaround: Use one of the following:

Manage Help Settings for SQL Server

  • Use the option Choose online or local help and configure help for "I want to use online help".

  • Use the option Install content from online and download the SQL Server 2014 Content.

F1 Help: By design when you press F1 in SQL Server Management Studio, the online version of the F1 Help topic is displayed in the browser. This occurs even when you have installed local Help.

Updating content:
In SQL Server Management Studio and Visual Studio, the Help Viewer application may freeze (hang) during the process of adding the documentation. To resolve this issue, do the following. For more information about this issue, see Visual Studio Help Viewer freezes.

  • Open the %LOCALAPPDATA%\Microsoft\HelpViewer2.2\HlpViewer_SSMS16_en-US.settings | HlpViewer_VisualStudio14_en-US.settings file in Notepad and change the date in the following code to some date in the future.
     Cache LastRefreshed="12/31/2017 00:00:00"    

horizontal_bar

Product Documentation (RC3)

Issue and customer impact: A downloadable version of the SQL Server 2016 documentation is not yet available. When you use Help Library Manager to attempt to Install content from online, you will see the SQL Server 2012 and SQL Sever 2014 documentation but there are no options for SQL Server 2016 documentation.

Workaround: Use one of the following:

Manage Help Settings for SQL Server

  • Use the option Choose online or local help and configure help for "I want to use online help".

  • Use the option Install content from online and download the SQL Server 2014 Content.

F1 Help: By design when you press F1 in SQL Server Management Studio, the online version of the F1 Help topic is displayed in the browser. This occurs even when you have installed local Help.

Updating content:
In SQL Server Management Studio and Visual Studio, the Help Viewer application may freeze (hang) during the process of adding the documentation. To resolve this issue, do the following. For more information about this issue, see Visual Studio Help Viewer freezes.

  • Open the %LOCALAPPDATA%\Microsoft\HelpViewer2.2\HlpViewer_SSMS16_en-US.settings | HlpViewer_VisualStudio14_en-US.settings file in Notepad and change the date in the following code to some date in the future.
     Cache LastRefreshed="12/31/2017 00:00:00"    

PolyBase (RC3)

PolyBase queries may fail after upgrade from RC1 or previous releases.

Issue and customer impact: After upgrading from SQL Server 2016 RC1 or previous release, PolyBase queries, import and export may fail with the following error: “Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase.”

Workaround

  • Uninstall PolyBase. In the Control Panel, click Uninstall a program, click Microsoft SQL Server 2016, click Remove. In the Remove SQL Server 2016 wizard select the instance with the failed PolyBase installation and click Next. On Features, click PolyBase Query Service for External Data. It is not necessary to remove other features that were successfully installed. Complete the steps of Remove SQL Server 2016.

  • Re-install PolyBase. Run setup, and add PolyBase feature on the same SQL Server instance.

Applies To: SQL Server 2016 RC3 when upgrading from RC1 or previous releases.

MS_Logo_X-Small

Community Additions

ADD
Show: