{"id":14611,"date":"2015-11-30T15:10:00","date_gmt":"2015-11-30T23:10:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/dataplatforminsider\/2015\/11\/30\/sql-server-2016-community-technology-preview-3-1-is-available\/"},"modified":"2024-01-22T22:50:23","modified_gmt":"2024-01-23T06:50:23","slug":"sql-server-2016-community-technology-preview-3-1-is-available","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2015\/11\/30\/sql-server-2016-community-technology-preview-3-1-is-available\/","title":{"rendered":"SQL Server 2016 Community Technology Preview 3.1 is available"},"content":{"rendered":"
The SQL Server engineering team is pleased to announce the immediate availability of SQL Server 2016 November public preview release CTP 3.1.<\/p>\n
To learn more about SQL Server 2016, 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 Have questions?\u00a0Join 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\u00a0through Microsoft\u2019s Connect tool<\/a>. We look forward to hearing from you.<\/p>\n New In-Memory OLTP<\/strong> improvements in CTP3.1 include:<\/p>\n Example<\/strong>: Illustrate the new features using a memory-optimized table natively compiled stored procedure.<\/p>\n CREATE TABLE<\/span> Sales.Store_inmem(<\/span> CREATE PROCEDURE<\/span> Sales.usp_InsertStore<\/span> DECLARE<\/span> @Demographics nvarchar(<\/span>max<\/span>)<\/span> =<\/span> REPLICATE<\/span>(<\/span>N’LOBtest’<\/span>,<\/span> 10000)<\/span> <\/span> Programmability improvement – AT TIME ZONE clause Syntax inputdate AT TIME ZONE timezone.<\/p>\n SELECT<\/span> SalesOrderID, OrderDate, TODATETIMEOFFSET<\/span> (<\/span>OrderDate, ‘-07:00’<\/span>)<\/span> as<\/span> OrderDatePST,<\/span> If inputdate is without provided offset information, function applies offset of the time zone assuming that value was originally provided in that time zone:<\/p>\n SELECT<\/span> convert<\/span>(<\/span>datetime2<\/span>, ‘2015-06-27 11:20:08.5783475’<\/span>)<\/span> <\/span> SELECT<\/span> convert<\/span>(<\/span>datetime2<\/span>, ‘2014-11-04 11:15:30.3214560’<\/span>)<\/span> <\/span> If inputdate contains offset, then function performs conversion to destination time zone:<\/p>\n SELECT<\/span> convert<\/span>(datetimeoffset<\/span>, ‘2015-06-27 11:20:08.5783475 +02:00’<\/span>)<\/span><\/span> SELECT<\/span> convert<\/span>(<\/span>datetimeoffset<\/span>, ‘2014-11-04 10:15:30.3214560 +00:00’<\/span>)<\/span> <\/span> SQL Server Analysis Services (SSAS)<\/strong> updates allow upgrading your existing models to 1200 compatibility level and a JSON editor for SSDT.<\/p>\n SQL Server PowerPivot and Reporting Services\/Power View for SharePoint 2016<\/strong> available now with CTP3.1! Make sure you use SharePoint Server 2016 Beta 2 available for download here<\/a>. Earlier versions of SharePoint Server are not supported. You also need Office Online Server Preview<\/a> because SharePoint Server no longer includes Excel Services. Excel Services, now called Excel Online Server, is now only available with Office Online Server. PowerPivot and Reporting Services\/Power View for SharePoint 2016 therefore require Office Online Server.<\/p>\n For more information, see What’s New in SQL Server 2016<\/a> and SQL Server 2016 Release Notes<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" The SQL Server engineering team is pleased to announce the immediate availability of SQL Server 2016 November public preview release CTP 3.1. To learn more about SQL Server 2016, visit the SQL Server 2016 preview page. To experience the new, exciting features in SQL Server 2016 and the new rapid release model, download the preview<\/p>\n","protected":false},"author":1457,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ms_queue_force_push":false,"ms_queue_id":"","ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","footnotes":""},"post_tag":[],"product":[5227,2403],"content-type":[2448],"topic":[],"coauthors":[2487],"class_list":["post-14611","post","type-post","status-publish","format-standard","hentry","product-sql","product-sql-server-2016","content-type-updates","review-flag-1593580419-556","review-flag-1593580427-503","review-flag-1-1593580431-15","review-flag-2-1593580436-981","review-flag-3-1593580441-293","review-flag-new-1593580247-437","review-flag-publi-1593580761-761"],"yoast_head":"\n\n
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0[BusinessEntityID] int IDENTITY<\/span> NOT NULL<\/span> PRIMARY KEY NONCLUSTERED<\/span>,<\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0[Name] nvarchar<\/span>(<\/span>200)<\/span> NOT NULL<\/span>,<\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0[SalesPersonID] int<\/span> NULL<\/span>,<\/span>
\n[Demographics] nvarchar<\/span>(<\/span>max<\/span>)<\/span> NULL<\/span>, — LOB column<\/span><\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0[ModifiedDate] datetime2<\/span> NOT NULL<\/span> DEFAULT<\/span> (<\/span>sysdatetime<\/span>())<\/span>,<\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0INDEX<\/span> ix_SalesPersonID NONCLUSTERED<\/span> (SalesPersonID), — index on Nullable column<\/span><\/span>
\nINDEX<\/span> ix_Name UNIQUE NONCLUSTERED<\/span> (<\/span>Name)<\/span> — UNIQUE index<\/span><\/span>
\n) WITH<\/span> (MEMORY_OPTIMIZED=ON<\/span>)<\/span>
\nGO<\/span><\/p>\n
\n@Name nvarchar<\/span>(<\/span>200)<\/span> NOT NULL<\/span>,<\/span>
\n@SalesPersonID int<\/span> = NULL<\/span>,<\/span>
\n@Demographics nvarchar<\/span>(<\/span>max<\/span>)<\/span> = NULL<\/span><\/span>
\nWITH NATIVE_COMPILATION, SCHEMABINDING<\/span>
\nAS<\/span>
\nBEGIN ATOMIC WITH<\/span> (<\/span>TRANSACTION ISOLATION LEVEL<\/span>=SNAPSHOT<\/span>, LANGUAGE<\/span>=N’Dutch’<\/span>)<\/span><\/span>
\nINSERT<\/span> Sales.Store_inmem (<\/span>Name, SalesPersonID, Demographics)<\/span> <\/span>
\nVALUES<\/span> (<\/span>@Name, @SalesPersonID, @Demographics)<\/span><\/span>
\n\u00a0<\/span>
\nEND<\/span>
\nGO<\/span><\/p>\n
\nEXECUTE Sales.usp_InsertStore @Name=‘test’<\/span>, @Demographics=@Demographics<\/span>
\nSELECT *<\/span> FROM<\/span> Sales.Store_inmem<\/span>
\nGO<\/span><\/p>\n
\nSupport for AT TIME ZONE clause that allows customers to convert datetime values across different time zones, honoring time zone conversion rules. It can be used to appropriately present datetime values in applications that target international markets.<\/p>\n\n
Examples<\/h1>\n
\nTODATETIMEOFFSET<\/span> (<\/span>OrderDate, ‘-07:00’<\/span>)<\/span> AT TIME ZONE<\/span> ‘Central European Standard Time’<\/span> AS<\/span> OrderCETTime<\/span>
\nFROM<\/span> Sales.[SalesOrderHeader]<\/span><\/p>\n
\nAT TIME ZONE<\/span> ‘Central European Standard Time’<\/span> as<\/span> CETTimeWithOffset<\/span><\/p>\n
\nAT TIME ZONE<\/span> ‘Central European Standard Time’<\/span> as<\/span> CETTimeWithOffset<\/span><\/p>\n
\nAT TIME ZONE<\/span> ‘Pacific Standard Time’<\/span> as<\/span> PacificStandardTime<\/span><\/p>\n
\nAT TIME ZONE<\/span> ‘Pacific Standard Time’<\/span> as<\/span> PacificStandardTime<\/span><\/p>\n