| title | SQL Server vNext Release Notes | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 03/12/2017 | |
| ms.prod | sql-vnext | |
| ms.reviewer | ||
| ms.suite | ||
| ms.technology |
|
|
| ms.tgt_pltfrm | ||
| ms.topic | article | |
| ms.assetid | 13942af8-5a40-4cef-80f5-918386767a47 | |
| caps.latest.revision | 41 | |
| author | craigg-msft | |
| ms.author | craigg | |
| manager | jhubbard |
This topic describes limitations and issues with [!INCLUDEssSQLv14_md].
- To read what's new in this release, see What's New in SQL Server vNext.
- SQL Server on Linux Release notes are published on our new and growing documentation platform.
- SQL Server Reporting Services release notes are published within the Reporting Services section.
Try it out:
Download [!INCLUDEssSQLv14_md] from the Evaluation Center
- Issue and customer impact: Documentation for [!INCLUDEssSQLv14_md] is limited and content is included with the [!INCLUDEssSQL15_md] documentation set. Content in articles that is specific to [!INCLUDEssSQLv14_md] will be noted with Applies To.
- Issue and customer impact: No offline content is available for [!INCLUDEssSQLv14_md].
[!INCLUDEssSQLv14_md] is intended as a test version only. Production deployments are not supported. It is recommneded you install and test [!INCLUDEssSQLv14_md] on a virtual machine.
- Issue and customer impact: Documentation for [!INCLUDEssSQLv14_md] is limited and content is included with the [!INCLUDEssSQL15_md] documentation set. Content in articles that is specific to [!INCLUDEssSQLv14_md] will be noted with Applies To.
- Issue and customer impact: No offline content is available for [!INCLUDEssSQLv14_md].
- Issue and customer impact: The CDC Control Task, CDC Source, and CDC Splitter in are not supported in this CTP release.
- Workaround: There is no workaround.
[!INCLUDEssSQLv14_md] is intended as a test version only. Production deployments are not supported. It is recommneded you install and test [!INCLUDEssSQLv14_md] on a virtual machine.
- Issue and customer impact: In some cases, the MSSQLSERVER service will get stuck in the "Starting" state.
- Workaround: To work around this issue:
- Create a dependency between the
mssqlserverservice and thekeyisoservice. One way to do this is to run the following from an elevated Command Prompt:sc config mssqlserver depend= keyiso - Reboot the computer.
- Create a dependency between the
- Issue and customer impact: Documentaion for [!INCLUDEssSQLv14_md] is limited and content is inlcuded with the [!INCLUDEssSQL15_md] documentation set. Content in articles that is specific to [!INCLUDEssSQLv14_md] will be noted with Applies To:.
- Issue and customer impact: No offline content is available for [!INCLUDEssSQLv14_md].
Issue and customer impact: When the SSIS Scale Out feature is installed on a computer, deleting the SSISDB catalog database may fail with following error: “Could not drop login 'login' as the user is currently logged in”.
Workaround:
- On a Scale Out Master computer, run the command “services.msc” to open the Services window. Stop the SQL Server Integration Services Cluster Master service.
- On Scale Out Worker computers that connect to the master, run the command "services.msc" to open the Services window. Stop the SQL Server Integration Services Cluster Worker service.
You can now delete the SSISDB catalog database.
Issue and customer impact: When the entity transaction log type is set to Attribute in [!INCLUDEssMDSshort_md] (default value is Member), the following scenarios fail:
- Transactions for entity changes are not shown in the website.
- Unable to open the Transactions page on the website and reverse a transaction.
- Unable to update an entity with a transaction annotation, in the website.
Workaround: There is no workaround.
- Issue and customer impact: When the Copy only committed version setting is set to No (default value is Yes), the copy version operation may fail. There is no error message.
- Workaround: There is no workaround.
[!INCLUDEssSQLv14_md] is intended as a test version only. Production deployments are not supported. It is recommneded you install and test [!INCLUDEssSQLv14_md] on a virtual machine.
Specifically, while the following scenarios may work for you, they have not been thoroughly tested and are not supported in [!INCLUDEssSQLv14_md]:
- Uninstall of CTP 1.1.
- Side by side installation with any other versions of SQL Server.
- Upgrade from any previous versions of SQL Server.
- No SQL Server feature pack components are available as part of the [!INCLUDEssSQLv14_md] installation.
- Issue and customer impact: Documentation for [!INCLUDEssSQLv14_md] is limited and content is included with the [!INCLUDEssSQL15_md] documentation set. Content in articles that is specific to [!INCLUDEssSQLv14_md] will be noted with Applies To:.
- Issue and customer impact: No offline content is available for [!INCLUDEssSQLv14_md].
Issue and customer impact: When the entity transaction log type is set to Attribute in [!INCLUDEssMDSshort_md] (default value is Member), the following scenarios fail:
- Transactions for entity changes are not shown in the website.
- Unable to open the Transactions page on the website and reverse a transaction.
- Unable to update an entity with a transaction annotation, in the website.
Workaround: There is no workaround.
- Issue and customer impact: When the Copy only committed version setting is set to No (default value is Yes), the copy version operation may fail. There is no error message.
- Workaround: There is no workaround.
Issue and customer impact: When the SSIS Scale Out feature is installed on a computer, deleting the SSISDB catalog database may fail with following error: “Could not drop login 'login' as the user is currently logged in”.
Workaround:
- On a Scale Out Master computer, run the command “services.msc” to open the Services window. Stop the SQL Server Integration Services Cluster Master service.
- On Scale Out Worker computers that connect to the master, run the command "services.msc" to open the Services window. Stop the SQL Server Integration Services Cluster Worker service.
You can now delete the SSISDB catalog database.
Issue and customer impact: The ODBC Connection Manager, Source, and Destination are not supported in this CTP release.
Workaround: There is no workaround.
[!INCLUDEssSQLv14_md] is intended as a test version only. Production deployments are not supported. It is recommneded you install and test [!INCLUDEssSQLv14_md] on a virtual machine.
Specifically, while the following scenarios may work for you, they have not been thoroughly tested and are not supported in [!INCLUDEssSQLv14_md]:
- Uninstall of CTP 1.0.
- Side by side installation with any other versions of SQL Server.
- Upgrade from any previous versions of SQL Server.
- No SQL Server feature pack components are available as part of the [!INCLUDEssSQLv14_md] installation.
- Issue and customer impact: Documentaion for [!INCLUDEssSQLv14_md] is limited and content is inlcuded with the [!INCLUDEssSQL15_md] documentation set. Content in artilces that is specific to [!INCLUDEssSQLv14_md] will be noted with Applies To:.
- Issue and customer impact: No offline content is avaiable for [!INCLUDEssSQLv14_md].
-
Issue and customer impact: The
STRING_AGGfunction in CTP1 returns LOB type as a result (e.g.NVARCHAR(MAX)). In a future CTP release, this behavior might change andSTRING_AGGmight returnNVARCHAR(4000)if input values are not LOB types. An overflow error might be thrown if the concatenated results cannot fit intoNVARCHAR(4000). -
Issue and customer impact: Avoid usages of non-reserved keywords such as
WITHINas an alias forSTRING_AGGexpressions. (For exampleSELECT Company.Name, STRING_AGG(Product.Name, ',') AS WITHIN FROM TableA;.) In a future CTP release,WITHINtoken afterSTRING_AGGcall might be used as a part ofSTRING_AGGfunction. -
Workaround: Avoid using
WITHINalias or addAS WITHINas an alias specification in order to avoid collisions with future changes that might be added inSTRING_AGGfunction.
Issue and customer impact: Stopping an operation in [!INCLUDEssIS_md] using [!INCLUDEssManStudio_md] or the catalog.stop_operation stored procedure, may fail with following error: “A .NET Framework error occurred during execution of user-defined routine or aggregate 'stop_operation_internal'”.
- Workaround: Open the Windows Task Manager. On the Processes Tab, find the process named ISServerExec and click End Task to end the process.
Issue and customer impact: Creating a dump for the execution of a package by using the catalog.create_execution_dump stored procedure, may fail with following error: “A .NET Framework error occurred during execution of user-defined routine or aggregate 'create_execution_dump_internal'”.
- Workaround: Open the Windows Task Manager. On the Processes Tab, find the process named ISServerExec, right click the process, and then click Create dump file.
Issue and customer impact: Querying the [!INCLUDEssIS_md] perf counters by using the table-valued function, catalog.dm_execution_performance_counters, may fail with following error: “A .NET Framework error occurred during execution of user-defined routine or aggregate 'get_execution_perf_counters'”.
- Workaround: Use the Windows Performance Monitor to monitor the perf counters values directly. There is no workaround for perf counters that are for a specific package execution.
Issue and customer impact: When the [!INCLUDEssIS_md] Scale Out feature is installed on a machine, deleting the SSISDB catalog may fail with following error: “Could not drop login ‘…’ as the user is currently logged in”.
Workaround:
-
On a Scale Out Master machine, run the command “services.msc” to open the Services window and stop the SQL Server Integration Services Cluster Master service.
-
On Scale Out Worker machines, which connect to the master, run the command "services.msc" to open the Services window. Stop the SQL Server Integration Services Cluster Worker service.
You should now be able to delete the SSISDB catalog.
- Issue and customer impact: ODCB connector in [!INCLUDEssIS_md] is not supported.
- Workaround: There is no workaround.
SQL Server Reporting Services isn't releasing any new features for [!INCLUDEssSQLv14_md].
Issue and customer impact: When the entity transaction log type is set to Attribute in [!INCLUDEssMDSshort_md] (default value is Member), the following scenarios fail:
- Transactions for entity changes are not shown in the website.
- Unable to open the Transactions page on the website and reverse a transaction.
- Unable to update an entity with a transaction annotation, in the website.
Workaround: There is no workaround.
Issue and customer impact: When the Copy only committed version setting is set to No (default value is Yes), the copy version operation may fail. There is no error message.
Workaround: There is no workaround.
SQL Server Management Studio is a seperate downlaod. For the latest information, see SQL Server Management Studio - Release Notes.


