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
17 reads
A lot has been written about the change of licencing in SQL 2016 SP1. Here's my two-pence worth.
2017-05-17
17 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
16 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
10 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
10 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,642 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,366 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,364 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,485 reads
By alevyinroc
T-SQL Tuesday is a monthly blog party hosted by a different community member each...
By Vinay Thakur
As Open Source – PostgreSQL and AI is a growing and powerful DB system,...
By gbargsley
A New Chapter: Why I Made the Move from Dayforce to ESO Over the...
Comments posted to this topic are about the item How Clustering can be Used...
Comments posted to this topic are about the item Moving the Error Log
Comments posted to this topic are about the item A Security and AI Fail
How can I change the location in which the SQL Server error log is written in SQL Server 2025?
See possible answers