{"id":14931,"date":"2016-03-07T09:45:44","date_gmt":"2016-03-07T17:45:44","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/dataplatforminsider\/?p=14931"},"modified":"2024-01-22T22:50:25","modified_gmt":"2024-01-23T06:50:25","slug":"technical-overview-sql-server-2016-release-candidate-0","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2016\/03\/07\/technical-overview-sql-server-2016-release-candidate-0\/","title":{"rendered":"Technical Overview: SQL Server 2016 Release Candidate 0"},"content":{"rendered":"
The SQL Server engineering team is pleased to announce the availability of SQL Server 2016 Release Candidate 0. This is an important milestone in the release of SQL Server 2016, as it marks feature completion for most dimensions of the product and means a very rich set of capabilities are now available. These include: real-time operational analytics, rich visualizations on mobile devices, built-in advanced analytics, new advanced security technologies, and new hybrid scenarios allowing you to securely stretch data to the cloud.<\/p>\n
To learn more about the release, visit the SQL Server 2016 preview page<\/a>. To experience the new, exciting features in SQL Server 2016 and the new rapid release model, download the preview<\/a> and start evaluating the impact these new innovations can have for your business.<\/p>\n Questions? Join the discussion of the new SQL Server 2016 capabilities at MSDN<\/a> and StackOverflow<\/a>. If you run into an issue or would like to make a suggestion, you can let us know using Microsoft\u2019s Connect tool<\/a>. We look forward to hearing from you.<\/p>\n For more information on this release, see SQL Server 2016 Release Notes<\/a> and What’s New in SQL Server 2016<\/a>.<\/p>\n This release now supports a new database level object that holds optional configuration values that affect the behavior of the application code at the database level. This support is available in both SQL Server 2016 Release Candidate (RC0) and SQL Database V12 using the new ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL) statement. This statement modifies the default SQL Server 2016 Database Engine behavior for a particular database. A generic mechanism for creating database configuration(s) at creation time is not provided.<\/p>\n These options are:<\/p>\n The following T-SQL Syntax is supported:<\/p>\n ALTER DATABASE SCOPED CONFIGURATION < set_options > ::= The new functionality is supported for both Azure SQL Database and SQL Server.<\/p>\n PolyBase<\/strong> enhancements in RC0 include:<\/p>\n SQL Server Management Studio improvements in this release include:<\/p>\n In-Memory OLTP<\/strong> new features in RC0:<\/p>\n With CTP3.3, we added support for efficient DELETE operations for tables with up to 10,000 incoming foreign key references. With RC0, we are adding support for the following:<\/p>\n The following limitations still apply:<\/p>\n STRING_SPLIT is a T-SQL function that splits input character expression by specified separator and outputs result as a table.<\/p>\n Syntax:<\/strong><\/p>\n STRING_SPLIT ( string, separator ) Examples:<\/strong><\/p>\n Split comma separated value literal string The result is:<\/p>\n value Split comma separated value string in a column Data stored in a UTF-8 encoded file can now be imported into SQL Server and exported from SQL Server into a UTF-8 encoded file, using BULK INSERT<\/strong> T-SQL command and bcp<\/strong> command line utility. As a part of the import process, the UTF-8 encoded strings are read from the file, and converted and stored as native data types that correspond to the target columns in SQL Server tables. As a part of the export process, data are converted from native data types into UTF-8 encoded strings and written into the file. All native data types are supported except Xml, SqlVariant, Text, NText, and Image. The UTF-8 code page is specified by providing the following arguments:<\/p>\n Examples:<\/strong><\/p>\n Importing with BULK INSERT into SQL Server from a file Importing with bcp utility into SQL Server from a file Exporting with bcp utility from SQL Server to a file AlwaysOn Availability Groups<\/strong> add support for:<\/p>\n This month\u2019s update to Analysis Services delivers support for display folders for Tabular models, any models created with new SQL Server 2016 compatibility level can now be used with PowerShell and SSIS. Finally, the new Tabular Object model is released to allow easier development and maintenance through code against tabular models. See the Analysis Services blog for more details.<\/p>\n Much more functionality is now available in this next preview of the new Reporting Services web portal. You can now:<\/p>\n SSIS Projects in Visual Studio SQL Server Data Tools (SSDT) can now target 2012, 2014 and 2016 versions of SQL Server by switching a project level property between 2012, 2014 and 2016 SQL server. SSIS now supports setting a server wide customized logging level. Finally, the SSIS HDFS connector now supports the ORC file format, in addition to CSV and Avro. See the Integration Services blog for more details.<\/p>\n Master Data Services (MDS)<\/strong> adds a New Derived Hierarchy Management web page. See the Master Data Services blog for more details.<\/p>\n For more information on this release, see SQL Server 2016 Release Notes<\/a> and What’s New in SQL Server 2016<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" The SQL Server engineering team is pleased to announce the availability of SQL Server 2016 Release Candidate 0. This is an important milestone in the release of SQL Server 2016, as it marks feature completion for most dimensions of the product and means a very rich set of capabilities are now available. These include: real-time<\/p>\n","protected":false},"author":1457,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ep_exclude_from_search":false,"_classifai_error":"","footnotes":""},"post_tag":[],"product":[5227,2403],"content-type":[2424,2448],"topic":[2466],"coauthors":[2487],"class_list":["post-14931","post","type-post","status-publish","format-standard","hentry","product-sql","product-sql-server-2016","content-type-best-practices","content-type-updates","topic-developer","review-flag-1593580427-503","review-flag-1-1593580431-15","review-flag-2-1593580436-981","review-flag-3-1593580441-293","review-flag-5-1593580452-31","review-flag-8-1593580467-480","review-flag-new-1593580247-437"],"yoast_head":"\nDatabase scoped configuration<\/h2>\n
\n
\n<\/strong>
\n{
\n{ [ FOR SECONDARY] SET }
\n}
\n| CLEAR PROCEDURE_CACHE
\n[;]<\/p>\n
\n{
\nMAXDOP = { | PRIMARY}
\n| LEGACY_CARDINALITY_ESTIMATION = { ON | OFF | PRIMARY}
\n| PARAMETER_SNIFFING = { ON | OFF | PRIMARY}
\n| QUERY_OPTIMIZER_HOTFIXES = { ON | OFF | PRIMARY}
\n}<\/p>\n\n
\n
Improved support for large number of foreign key references<\/h2>\n
\n
\n
New Built-in Table-Valued Function STRING_SPLIT<\/h2>\n
\nreturns: table with a column named value<\/p>\n
\n<\/em>SELECT <\/span>* FROM<\/span> STRING_SPLIT<\/span>(‘Lorem ipsum dolor sit amet.’<\/span>, ”<\/span>)<\/p>\n
\n—–
\nLorem
\nipsum
\ndolor
\nsit
\namet.<\/p>\n
\n<\/em>SELECT<\/span> id, title, value
\nFROM<\/span> Article
\nCROSS APPLY<\/span> STRING_SPLIT<\/span>(tags, ‘,’<\/span>)<\/p>\nSupport for import and export of UTF-8 data<\/h2>\n
\n
\n<\/em>BULK INSERT<\/span><\/strong> MyTable
\nFROM<\/span><\/strong> ‘path\\file.csv’
\nWITH<\/span><\/strong> ( FIELDTERMINATOR<\/span><\/strong> = ‘,’, CODEPAGE <\/strong>= ‘65001’, DATAFILETYPE<\/strong> = ‘Char’<\/span>)<\/p>\n
\n<\/em>bcp<\/span><\/strong> MyTable in<\/span><\/strong>\u00a0\u00a0 “path\\file.csv” -T -t , -c -C 65001<\/span><\/p>\n
\n<\/em>bcp<\/strong><\/span> MyTable out<\/span><\/strong> “path\\file.csv” -T -t , -c -C 65001<\/span><\/p>\n\n
SQL Server Analysis Services (SSAS)<\/h2>\n
SQL Server Reporting Services (SSRS)<\/h2>\n
\n
SQL Server Integration Services (SSIS)<\/h2>\n