TDE and backup compression – still not working?
Until SQL 2016 if you used TDE (Transparent Data Encryption) you couldn’t use backup compression.
In 2016 Microsoft changed this, but...
2019-04-26 (first published: 2018-02-16)
2,391 reads
Matthew McGiffen
- Twitter: @MattMcGiffen
- Website: https://matthewmcgiffen.com/
There’s Still a Place for SQL Server Profiler
Follow a few of the SQL Family on Twitter and you’ll mostly see one view regards SQL Profiler, and it’s...
2019-04-26 (first published: 2018-07-25)
2,259 reads
Think twice before using table variables
T-SQL Tuesday
For T-SQL Tuesday this month Raul Gonzalez has asked us all to blog about lessons learnt the hard way:
http://www.sqldoubleg.com/2017/07/03/tsql2sday-92-lessons-learned-the-hard-way/
My...
2019-04-26 (first published: 2017-07-11)
8,851 reads
T-SQL Tuesday 107 – Viral Demo
For this month’s T-SQL Tuesday. Jeff Mlakar invites to talk about “a project you worked on or were impacted by...
2019-04-26 (first published: 2018-10-09)
1,869 reads
Understanding Keys and Certificates with Always Encrypted
Always Encrypted on SQL 2016 is pretty easy to set up. There’s even a single wizard to guide you through...
2019-04-26 (first published: 2017-05-30)
8,477 reads
Understanding Keys and Certificates with Transparent Data Encryption (TDE)
I’ve been taking a bit of a deep dive into understanding Transparent Data Encryption (TDE). As part of that I’ve...
2019-04-26 (first published: 2017-12-12)
2,784 reads
Using the built-in System Health session
When Microsoft introduced Extended Events (XE) in 2008, they also gave us a built-in XE session called system_health (though it’s...
2019-04-26 (first published: 2018-08-01)
5,368 reads
Using the Sequence Object to Generate Reference Numbers
The SEQUENCE object was added to T-SQL in SQL Server 2012. It’s reasonably well known to DBAs, but less so...
2019-04-26 (first published: 2019-02-20)
4,165 reads
What is Transparent Data Encryption?
Transparent Data Encryption (TDE) was introduced in SQL 2008 as a way of protecting “at rest” data. It continues to...
2019-04-26 (first published: 2018-01-26)
2,158 reads
Attending a climate protest for the first time
This is a blog devoted to databases, but for once I’m going to go off topic and talk about something I did at the weekend that I’ve never done...
2019-04-25
19 reads
Blogs
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
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