Over the last year or so, I've been working on understanding the General Data Protection Regulation (GDPR) that is the data privacy law in Europe. This has been law for a couple years, but enforcement just started in May of 2018. Along the way, I spent time looking at other countries and the various types of data protection laws they've enacted or are preparing. The US was included in this research, though in a woeful, sad way.
The US hasn't had much in the way of data protection, at least not at the national level. Since the US is a large market, many of us wondered if their reluctance would influence the rest of the world to care less about data protections or even weaken the GDPR by attracting more business away from Europe. That would be disappointing, as I think the state of data security, protections for humans, and privacy rights are extremely poor in the US.
At the state level, New York introduced the SHIELD Act, though it hasn't been passed. Most other US states aren't working on anything, but California has actually passed a law, similar to the GDPR. I'm happy to see this, and my hope is that this pressures Congress to pass something that will apply to all 50 states. However, even if they don't, perhaps California will influence the rest of us. I suspect many companies will want to do business in the state, but not want separate rules for one state v others, so they'll just adopt CA standards.
The bill was a little rushed, in part to head off a ballot initiative. Whether this is good or bad remains to be seen, but plenty of the large technology companies don't like it. Google and Facebook for sure, but I'm sure many tech companies that make profits from collecting, analyzing, using, and selling data are going to be upset. This could cause issues with their business models, and my guess is they'll fight any fines and appeal court rulings for years.
Personally I understand there is business value in data, and there are plenty of good uses of data. What I don't like, or appreciate, is companies looking for new ways to gather data on me without limits, and certainly without my consent or understanding. We don't really know how valuable and potentially dangerous data is about each of us, and we ought to have some rights and control over it's use, storage, and retention.
Whether this will change our work as data professionals remains to be seen. My guess is we might finally get to treat data as not only an asset of the company, but as an asset of individuals that we need to safeguard and protect.
SQL Server Data Tools (SSDT) is a toolset which provides an environment for you to carry out all your database design work in SQL Server. It can be used to build to build SQL Server relational databases. More »
Could you spare a few minutes to help Redgate improve its products and services?
They’re running a survey of their users and the wider SQL Server community and they’d appreciate your insights. As a thank you for taking part, you’ll also be entered in a prize draw for a $250 Amazon Voucher.
In the second part of his series, Nicolas Prigent describes in detail how to automate the login process using PowerShell and Azure CLI. Nicolas also explains how to retrieve information about your Azure subscription. More »
Readers will learn by example how to use Microsoft SQL Server 2016 Integration Services (SSIS) as they design and implement extract, transform, and load (ETL) solutions to support a business application that integrates with a data warehouse and an online Web store across a heterogeneous system. This volume describes proven methods to support common ETL needs, such as databases communicating directly with each other, using files to exchange data, or performing database operations using Web services.
Pick up your copy of this great book today at Amazon today.
Yesterday's Question of the Day
(by Steve Jones):
When I create a new Azure SQL Database, must I include this in a resource group? Assume I am not using the classic deployment method.
Answer: No, but this will exist as a part of a default resource group for your subscription
The classic model for deploying Azure resources did not include grouping. However, when the Resource Manager was introduced, Resource Groups were added and all resources were added to a default group.
Now if you choose the classic deployment model and create resources without a resource group, they are still added to a default resource group.
Ref: Azure Resource Manager vs. classic deployment: Understand deployment models and the state of your resources - click here
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.