Skip to main content

SQL Server 2016 SP 1

By David Postlethwaite

SQL Server 2016 SP1 was released in November 2016 only five months after the initial release.

There have been some significant changes and additions in this release. The most significant of which is that many features that once only existed in Enterprise edition, such as Always Encrypted, partitioning, in memory, Columnstore and compression are now available in lower editions as well.

The image below shows a list of previous enterprise edition features that are now available in other editions:

SQL Server 2016 SP1 previous Enterprise-Only Features
SQL Server 2016 SP1 previous Enterprise-Only Features

The one feature that remains Enterprise only is Transparent Data Encryption (TDE) which is a shame given how important security is becoming.

So the main difference between Enterprise and Standard edition is now over the amount of memory and CPU they can access. With so many new features now available in standard edition there is even less reason not to move to SQL 2016. 

One new T-SQL command that was introduced in SQL 2016 was “DROP IF EXISTS”. So rather than writing a complicated query to check if an object exists before dropping it you can now simply say

DROP TABLE IF EXISTS [Person].[CountryRegion];

As a result of this there was a campaign to add a function that Oracle has had for a long time namely “CREATE or ALTER”. And in SP1 we now have it. You can now write:

CREATE OR ALTER PROCEDURE dbo.sp_MyProc as
BEGIN
PRINT 'This is a new Procedure';
END

These two commands can be used against most objects in SQL Server  2016. For those of you that write installation scripts for your applications these two new commands should make your code much easier to manage. 

Comments

Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…