New Microsoft Releases April 2016

New Microsoft Releases April 2016

SQL Server 2016 RC3 – last RC before RTM

Windows Server 2016 TP5 – Last TP before RTM

Window System Centre 2016 TP5 – Last TP before RTM

The big list of recent Microsoft releases include Technical Previews/Release Candidates

What’s new in Windows Server 2016 TP5

Windows Server 2016 TP5 issues,install CU KB3157663 before installing any server roles, features, or other products

Powershell module for docker in Window Server 2016 previews builds now deprecated, open source version released






DB2 LUW 11.1

DB2 11.1 has been announced with a download date of June 15 2016

Potential new features are:

Core workloads

Enterprise Encryption supports Centralized Key Managers (KMIP)

Support for Encryption to useĀ  KMIP 1.1 with a Centralized Key Manager

– update dbm cfg using keystore_type kmip

– update dbm cfg using keystore location /home/justdave/isklm.cfg

Config file contains host, port number etc.

Technology Preview of support for Hardware Security Modules

Simpler Deployment

Greater Availability

Zero Data Loss HADR

More online management

More platforms supported

Power Linux (LE) supported

Virtualization for RDMA (x86) supported

Very Large Database Performance

Faster throughput

Better upgrades

DB2 9.7 and higher can be directly upgraded to DB2 11.1 (support for upgrades from 3 releases back)

Online upgrades with no need for an offline backup.

A recovery procedure including roll-forward thtough a database upgrade exists. This does not include DPF and requires upgrading from DB2 10.5 FP7 or higher.

Steamlined HADR upgrade

HADR environments can be upgraded with need to re-initialized the secondary. This does not apply to Purescale and requires upgrading from DB2 10.5 FP7 or higher.

Warehousing workloads

MPP supports BLU

DPF renamed to MPP

Faster ELT/ETL Performance

More Query Workloads Optimized

More functions supported

Generated Columns


OLAP+BLU Performance increased

Multi-Lingual SQL Advances

Postgres syntax

Support for European Languages

Codepage 819


System.Transactions (and AlwaysOn Availability Groups)

With SQL Server 2016 AlwaysOn Availability Groups (on Windows Server 2016 TP4) supports MSDTC which can be used for transactions which access more than 1 database.

However there are Transactions which do not use MSDTC.

Within the .NET Framework there is System.Transactions namespace

As per these implement a Transaction Manager which can handle transactions within SQL Server.

System.Transactions only SOMETIMES escalates to MSDTC!

“As long as the System.Transactions infrastructure most one durable resource that supports single-phase notifications, the transaction remains in the ownership of the System.Transactions infrastructure”

The question then is with SQL Server 2016 AlwaysOn Availability Groups (on Windows Server 2016 TP4) and a transaction which uses more than 1 database

a) Does SQL Server 2016 AlwaysOn Availability Groups support single-phase notifications?

b) With SQL Server 2016 AlwaysOn Availability Groups does moreĀ  than 1 single database count as 1 durable resource or more than 1 durable resource?

As per tracing can be used to determine who promotes a transaction and why.