Latest Builds of SQL Server 2017 - SentryOne Team Blog

Latest Builds of SQL Server 2017

There is a Microsoft page that tracks new features and fixes in each new build:

There is also a Linux version:

These documents list all of the minutiae, which is great! Gone are the days of secret CTPs and discovering new features on your own, though we have described before ways to compare CTPs and RCs to earlier versions, if you still want to do that:

You can download the latest CTP for Windows here, and Aaron described how to download the latest for Linux here.

RC2

The second release candidate was published on August 2nd, 2017. (Details here.)

Latest @@VERSION:

Microsoft SQL Server 2017 (RC2) – 14.0.900.75 (X64)
  Jul 27 2017 08:53:49
  Copyright (C) 2017 Microsoft Corporation
  Developer Edition (64-bit) on …
RC1

The first release candidate was published on July 17th, 2017. (Details here.)

CTP 2.1

CTP 2.1 was released on May 17th, 2017.

What's new in CTP 2.1?

First, setup has already incorporated some recent changes – you can now choose Python for machine learning, there are new options for SSIS scale out, and you need to install Reporting Services completely separately:

For the engine, it seems the only addition is the DMF sys.dm_db_log_stats(), a handy summary of the information you can currently only get from DBCC LOGINFO:

SELECT
  recovery_model,
  total_vlf_count,
  active_vlf_count,
  total_log_size_mb,
  active_log_size_mb,
  log_truncation_holdup_reason
FROM sys.dm_db_log_stats(DB_ID());

Results:

(There are a bunch of other columns too.)

There are also a set of new environment variables you can pass to docker run to pre-configure things like instance name, TCP port, and even Availability Groups. More info.

CTP 2.0

CTP 2.0 was released on April 19th as part of the Data Amp event; the official blog post is here.

What's new in CTP 2.0?
  • Resumable online index rebuilds
  • A new IDENTITY_CACHE setting for ALTER DATABASE SCOPED CONFIGURATION.
  • Graph Processing (more details here).
  • Cross-database transactions in Availability Groups (blog post here).
  • Safer CLR by default (Joey D'Antoni goes into detail here).
  • Adaptive Query Processing.
  • During setup, tempdb initial data file size can now be set up to 256 GB.
  • A new column, is_enforced, in the sys.key_constraints catalog view.
  • A new inline TVF, sys.dm_os_file_exists, to replace xp_fileexist.
  • A new inline TVF, sys.dm_db_log_info, to replace DBCC LOGINFO.
  • A new DMV, sys.dm_db_tuning_recommendations, that extends Query Store to support the new Automatic Tuning feature. There are other catalog views around this, as well as a new sys.query_store_wait_stats DMV.
  • Based on a new error message, "49938 : The licensing PID was successully processed. The new edition is [%s]" – it seems there will be some additional capability around changing edition without a reinstall.
  • On the Windows side, Python joins R for performing in-database analytics.
  • On the Linux side, log shipping has been added to SQL Server Agent.
CTP 1.4

CTP 1.4 was made public on Friday, March 17th. The big highlight is SQL Server Agent on Linux, but we will update this space with other details soon. Latest @@VERSION:

Microsoft SQL Server vNext (CTP1.4) – 14.0.405.198 (X64)
  Mar 11 2017 01:54:12
  Copyright (C) 2016 Microsoft Corporation. All rights reserved.
  Developer Edition (64-bit) …
CTP 1.3

CTP 1.3 came out Friday, February 17th. Latest @@VERSION:

Microsoft SQL Server vNext (CTP1.3) – 14.0.304.138 (X64)
  Feb 13 2017 16:49:12
  Copyright (C) 2016 Microsoft Corporation. All rights reserved.
  Developer Edition (64-bit) …

Some cool things here, including resumable index rebuilds, both cross-platform and cluster-less Availability Groups, retention policies for temporal tables, and a new dynamic management function for exposing statistics histograms.

CTP 1.2

CTP 1.2 came out Friday, January 20th. Latest @@VERSION:

Microsoft SQL Server vNext (CTP1.2) – 14.0.200.24 (X64)
  Jan 10 2017 19:15:28
  Copyright (C) 2016 Microsoft Corporation. All rights reserved.
  Developer Edition (64-bit) …

The only change I've discovered so far in this CTP is the addition of several performance counters relating to In-Memory OLTP (and these aren't mentioned in the docs above):

object_name counter_name
SQL Server vNext XTP Cursors Cursor deletes/sec
SQL Server vNext XTP Cursors Cursor inserts/sec
SQL Server vNext XTP Cursors Cursor scans started/sec
SQL Server vNext XTP Cursors Cursor unique violations/sec
SQL Server vNext XTP Cursors Cursor updates/sec
SQL Server vNext XTP Cursors Cursor write conflicts/sec
SQL Server vNext XTP Cursors Dusty corner scan retries/sec (user-issued)
SQL Server vNext XTP Cursors Expired rows removed/sec
SQL Server vNext XTP Cursors Expired rows touched/sec
SQL Server vNext XTP Cursors Rows returned/sec
SQL Server vNext XTP Cursors Rows touched/sec
SQL Server vNext XTP Cursors Tentatively-deleted rows touched/sec
SQL Server vNext XTP Garbage Collection Dusty corner scan retries/sec (GC-issued)
SQL Server vNext XTP Garbage Collection Main GC work items/sec
SQL Server vNext XTP Garbage Collection Parallel GC work item/sec
SQL Server vNext XTP Garbage Collection Rows processed/sec
SQL Server vNext XTP Garbage Collection Rows processed/sec (first in bucket and removed)
SQL Server vNext XTP Garbage Collection Rows processed/sec (first in bucket)
SQL Server vNext XTP Garbage Collection Rows processed/sec (marked for unlink)
SQL Server vNext XTP Garbage Collection Rows processed/sec (no sweep needed)
SQL Server vNext XTP Garbage Collection Sweep expired rows removed/sec
SQL Server vNext XTP Garbage Collection Sweep expired rows touched/sec
SQL Server vNext XTP Garbage Collection Sweep expiring rows touched/sec
SQL Server vNext XTP Garbage Collection Sweep rows touched/sec
SQL Server vNext XTP Garbage Collection Sweep scans started/sec
SQL Server vNext XTP IO Governor Insufficient Credits Waits/sec
SQL Server vNext XTP IO Governor Io Issued/sec
SQL Server vNext XTP IO Governor Log Blocks/sec
SQL Server vNext XTP IO Governor Missed Credit Slots
SQL Server vNext XTP IO Governor Stale Rate Object Waits/sec
SQL Server vNext XTP IO Governor Total Rate Objects Published
SQL Server vNext XTP Phantom Processor Dusty corner scan retries/sec (Phantom-issued)
SQL Server vNext XTP Phantom Processor Phantom expired rows removed/sec
SQL Server vNext XTP Phantom Processor Phantom expired rows touched/sec
SQL Server vNext XTP Phantom Processor Phantom expiring rows touched/sec
SQL Server vNext XTP Phantom Processor Phantom rows touched/sec
SQL Server vNext XTP Phantom Processor Phantom scans started/sec
SQL Server vNext XTP Storage Checkpoints Closed
SQL Server vNext XTP Storage Checkpoints Completed
SQL Server vNext XTP Storage Core Merges Completed
SQL Server vNext XTP Storage Merge Policy Evaluations
SQL Server vNext XTP Storage Merge Requests Outstanding
SQL Server vNext XTP Storage Merges Abandoned
SQL Server vNext XTP Storage Merges Installed
SQL Server vNext XTP Storage Total Files Merged
SQL Server vNext XTP Transaction Log Log bytes written/sec
SQL Server vNext XTP Transaction Log Log records written/sec
SQL Server vNext XTP Transactions Cascading aborts/sec
SQL Server vNext XTP Transactions Commit dependencies taken/sec
SQL Server vNext XTP Transactions Read-only transactions prepared/sec
SQL Server vNext XTP Transactions Save point refreshes/sec
SQL Server vNext XTP Transactions Save point rollbacks/sec
SQL Server vNext XTP Transactions Save points created/sec
SQL Server vNext XTP Transactions Transaction validation failures/sec
SQL Server vNext XTP Transactions Transactions aborted by user/sec
SQL Server vNext XTP Transactions Transactions aborted/sec
SQL Server vNext XTP Transactions Transactions created/sec
CTP 1.1
Microsoft SQL Server vNext (CTP1.1) – 14.0.100.187 (X64)
  Dec 10 2016 02:51:11
  Copyright (C) 2016 Microsoft Corporation. All rights reserved.
  Developer Edition (64-bit) …
CTP 1.0
Microsoft SQL Server vNext (CTP1) – 14.0.1.246 (X64)
  Nov 1 2016 23:24:39
  Copyright (c) Microsoft Corporation
  Developer Edition (64-bit) …

Comments ( 0 )

    Leave A Comment

    Your email address will not be published.