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
15 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,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,363 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,484 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Wa:0817819444 Jl. Ahmad Yani No.9, RT.01/RW.05, Marga Jaya, Kec. Bekasi Sel., Kota Bks, Jawa...
Wa:0817819444 Jl. Panglima Sudirman No.35, Baturetno, Kec. Tuban, Kabupaten Tuban, Jawa Timur 62314
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers