I'm off today. Not taking a break, though perhaps it's a touch of a break. I'm actually in an airplane, heading to the UK for the first 2018 SQL in the City. We'll be broadcasting this Wednesday, and you can still register and watch. Let your boss know that you can get some cheap training (it's free), refresh yourself away from work, and you'll appreciate the perk as a part of your job. Maybe you'll even get to watch from the comfort of home.
Grant and Kathi are already in the UK enjoying SQL Bits, but this year I've been trying to do less travel and coaching volleyball more. My team of 14 year olds had a tournament yesterday, so I was blowing whistles and giving (loud) advice in a high school gym. Today I've got a laptop on a plane and am making my way a third of the way around the world. I may get to watch a movie, but there will certainly be a little demo practice as well.
The theme for this SQL in the City broadcast is Data Privacy and Protection. GDPR will start being enforced this spring, and many people around the world with be affected. Those outside the EU might not be sure of the ramifications of the regulation, but I wouldn't be surprised if similar legislation gets passed in other countries. In any case, the idea of ensuring you can control and protect data, with an eye on designing privacy for users into the system, is a good idea.
You can read the GDPR text, but that's what many of us have done and tried to interpret it for you. We have a great piece at SQLServerCentral and our product teams have been working hard to ensure that our products will help you improve your compliance. Lots of other vendors are doing the same thing, either working to change their policies or enhance products. Microsoft has certainly spent a lot of effort getting ready, and I'm sure they're not along in their efforts.
We all want better security for our data. Many of us empathize with the customers and clients about whom we collect data and often wish our systems provided better security, controls, and options. Sometimes our management doesn't agree, but certainly they feel the impact if we suffer a data breach. This Wednesday we'll be talking about Redgate products specifically, but also including general knowledge and ideas that you might use within your organization.
Register for the event and watch along on Wednesday. Ask questions and see how you can improve your data privacy. Most of our applications could use a little work on security, and we hope to help educate you on what you can do and how Redgate might be able to help.
The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music.
Write, format, analyze, and refactor SQL fast with SQL Prompt
Writing SQL is 50% faster with SQL Prompt. Your SQL code can be formatted just the way you like it, you can create and share snippets with your team, and with code analysis you get suggestions to improve your SQL as you type. Download your free trial
How to track every change to your SQL Server database
See who’s changing your database, alongside affected objects, date, time, and reason for the change with SQL Source Control. Get a full change history in your source control system. Learn more
If you’ve read anything about the upcoming General Data Protection Regulation (GDPR), you’ll probably have seen the phrase Data Privacy Impact Assessment (DPIA) used. This article explains exactly what it is, and outlines the four areas its expected to address. More »
Prepare for Microsoft Exam 70-761–and help demonstrate your real-world mastery of SQL Server 2016 Transact-SQL data management, queries, and database programming. Designed for experienced IT professionals ready to advance their status, Exam Ref focuses on the critical-thinking and decision-making acumen needed for success at the MCSA level. Get your copy from Amazon today.
Yesterday's Question of the Day
(by Evgeny Garaev):
What would you get by executing this query:
with cnumbers as
select 1 as i
where i < 10
Answer: The error - Recursive common table expression 'cnumbers' does not contain a top-level UNION ALL operator.
All anchor-member query definitions must be positioned before the first recursive member definition, and a UNION ALL operator must be used to join the last anchor member with the first recursive member.
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.