New Microsoft Releases April 2016Posted: April 30, 2016 Filed under: Uncategorized Leave a comment
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.1Posted: April 26, 2016 Filed under: DB2 11.1, DB2 LUW, Uncategorized | Tags: DB2 LUW Leave a comment
DB2 11.1 has been announced with a download date of June 15 2016
Potential new features are:
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
Zero Data Loss HADR
More online management
More platforms supported
Power Linux (LE) supported
Virtualization for RDMA (x86) supported
Very Large Database Performance
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.
MPP supports BLU
DPF renamed to MPP
Faster ELT/ETL Performance
More Query Workloads Optimized
More functions supported
OLAP+BLU Performance increased
Multi-Lingual SQL Advances
Support for European Languages
System.Transactions (and AlwaysOn Availability Groups)Posted: April 24, 2016 Filed under: Microsoft SQL Server, Microsoft SQL Server 2016, Uncategorized, Windows Server 2016 | Tags: Microsoft SQL Server, Microsoft SQL Server 2016, Windows Server 2016 Leave a comment
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 https://msdn.microsoft.com/en-us/library/system.transactions%28v=vs.110%29.aspx
As per https://msdn.microsoft.com/en-us/library/ms229978%28v=vs.110%29.aspx 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 handles..at 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 http://msdn.microsoft.com/en-us/library/ms229979.aspx tracing can be used to determine who promotes a transaction and why.