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
15 reads
A lot has been written about the change of licencing in SQL 2016 SP1. Here's my two-pence worth.
2017-05-17
15 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
781 reads
Thoughts on how to think about parallelism in SQL Server - and how to tune it.
2017-04-18
14 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
9 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,640 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,365 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,361 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,483 reads
Running AI and data pipelines on the edge instead of the cloud has gone...
By Steve Jones
While writing another post I realized my UNION query didn’t work as one might...
By James Serra
Since the release of my book Deciphering Data Architectures: Choosing Between a Modern Data...
Comments posted to this topic are about the item Secure Cached Plans
Comments posted to this topic are about the item Complex Data Processing with dbt...
Comments posted to this topic are about the item Over or Under Provisioned
The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?
See possible answers