Five reasons to run SQL Server 2016 on Windows Server 2016

The Microsoft SQL Server team is publishing a five-part series on why to run SQL Server 2016 on Windows Server 2016.  Can you guess reason #1?  

 Yes, it's security.  We're going to see a much bigger push on the MS front addressing its commitment to a holistic security approach across the whole Microsoft stack, building and integrating security throughout its platforms, and product and service offerings.  Read on to see how SQL Server 2016 on Windows Server 2016 increase your security posture, using features such as Device Guard, Credential Guard, Control Flow Guard and Windows Defender on Windows Server 2016 and Always Encrypted protection, Row-Level Security and Dynamic Data Masking in SQL Server 2016.

 https://blogs.technet.microsoft.com/hybridcloud/2017/03/23/five-reasons-to-run-sql-server-2016-on-windows-server-2016-1-security/

 The second part of the series focuses on the performance increases and cost savings that can be had with SQL Server 2016 on Windows Server 2016.
https://blogs.technet.microsoft.com/dataplatforminsider/2017/03/30/five-reasons-to-run-sql-server-2016-on-windows-server-2016-part-2/



Comments

  1. UnknownSeptember 2, 2017 at 12:05 AM

    Nice...Its highly informative post. I really enjoyed reading. Thanks

    ReplyDelete

Post a Comment

Popular posts from this blog

Microsoft Customer Guidance for WannaCrypt Attacks

As you no doubt are aware, the WannaCrypt attacks over the last couple of weeks have been quite pervasive. Microsoft has provided some guidance on the WannaCrypt attacks that I thought you should be aware of, both for Azure as well as on-premises. https://azure.microsoft.com/en-us/blog/wannacrypt-attacks-guidance-for-azure-customers/ https://blogs.technet.microsoft.com/msrc/2017/05/12/customer-guidance-for-wannacrypt-attacks/ Of note, Microsoft has released security patches for OS versions that are no longer in mainstream support, i.e. Windows XP, Windows 8 and Windows Server 2003.
Read more

ILM 2007 Certificate Management Customizations

ILM 2007, through its Certificate Management solution, or Certificate Lifecycle Manager (CLM) as it used to be known, allows an organization to manage credentials within their Windows Server 2003 and 2008 certification authorities. It acts like an administrative proxy, allowing you issue and manage digital certificates and smartcards through a web interface. The solution provides three different APIs (i.e. Provision, SQL and Notification) and a number of customizable interfaces, all of which allow you to customize CLM. This gives you the ability to greatly extend and expand the product's capabilities. For an overview of these APIs and interfaces, have a look at the Certificate Lifecycle Manager Overview on MSDN. Over the next few postings, I'll be looking at these APIs and interfaces in greater detail, to show you how they work and how they could be put to use in your CLM deployment. And I'd like to add a quick shout-out to David Lundell, over at ILM Best Practices , f
Read more