SQL Server 2016 SP1 – A significant change to licencing
A lot has been written about the change of licencing in SQL 2016 SP1. Here's my two-pence worth.
2017-05-17
9 reads
A lot has been written about the change of licencing in SQL 2016 SP1. Here's my two-pence worth.
2017-05-17
9 reads
A small change, but a great one, in SQL 2016 is native support for splitting strings.
This has to be about...
2017-05-09
780 reads
Thoughts on how to think about parallelism in SQL Server - and how to tune it.
2017-04-18
12 reads
In this post we’re going to create some encrypted columns in a table in a test database and look at some of the practicalities and limitations of working with...
2017-04-10
8 reads
This post attempts to explain in simple terms what keys are involved in Always Encrypted, how they get used, and the implications of those facts.
2017-04-03
9 reads
The European General Data Protection Regulation (GDPR) is coming, bringing new rules about the protection of Personally Identifiable Information (PII).
For...
2017-03-28
5,635 reads
This is a quickie post to introduce the new DBCC command CLONEDATABASE.
Okay so this isn’t technically a SQL Server 2016...
2019-04-26 (first published: 2017-03-20)
2,356 reads
Query Store was, probably without doubt, the most anticipated and talked out new feature in SQL 2016. Certainly by the...
2019-04-26 (first published: 2017-03-13)
6,338 reads
This is the first in a series of blog posts about how great SQL Server 2016 is, and why you should...
2017-02-23
1,475 reads
By Andy Warren
Somehow two years have elapsed since my last update; hopefully it won’t be that...
By Steve Jones
If someone is trying to convince you it’s not a pyramid scheme, it’s a...
By Steve Jones
I was looking back at my year and decided to see if SQL Prompt...
I have table: t1 in schema1 with 19 billion records. I have another table...
Comments posted to this topic are about the item Minimally Viable Security
Comments posted to this topic are about the item Encoding NULL
What is returned from this code in SQL Server 2025?
SELECT BASE64_ENCODE(NULL)See possible answers