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
10 reads
A lot has been written about the change of licencing in SQL 2016 SP1. Here's my two-pence worth.
2017-05-17
10 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
13 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,637 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,357 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,348 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,476 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers