May 23, 2018 at 10:53 am
Hi,
I'd like to know the pros and cons about SQL Server telemetry.
I think that a such feature is proper to do not install into a prod environment.
Any contributes for me, please? Thanks
May 23, 2018 at 12:04 pm
This was removed by the editor as SPAM
May 23, 2018 at 12:22 pm
pmscorca - Wednesday, May 23, 2018 10:53 AMHi,
I'd like to know the pros and cons about SQL Server telemetry.
I think that a such feature is proper to do not install into a prod environment.Any contributes for me, please? Thanks
In general I think the gist of what telemetry is meant for, improving a product, is great. I have issues with how it's gets implemented.
So many privacy policies evolve and change over time. So you are agreeing to something that is likely to change. And then what...does that mean you uninstall a product because the privacy policy changes to something incongruent with company standards, expectations? Hurry up and move to a new platform? How long will that take and how much will it cost?
The data may be aggregated when you agree but the product vendors can change that and those things often go unnoticed. And many of the privacy policies have some section where it says they do share information with third parties and the data would be subject to those third party policies. You have no idea who these third parties are, when they change, etc. You can find out through contacting corporate offices but its starting to get fairly time consuming if you want to keep up with all of that. It's almost like you need to hire privacy policy coordinators, something along those lines, who would be tasked with monitoring policies, changes, etc.
Being that there have already been quite a few incidents of mishandling customers data, I have a lot of reservations about how the data is used. And for more "raw" data how do you know it's actually protected and won't be suspect to breaches? There have been quite a few breeches that have been the result of employees downloading data to their laptops, spreadsheets, things along those lines. Being that you don't know how the data is protected, I would be on the more cautious side and assume it's not protected against things like that.
On a production server, I'd rather not have the server resources used for something like this. For SQL Server, with the bugs/issues with updates, I'm not convinced that their process wouldn't cause problems. Things don't seem to be tested anywhere close to what they were in the past. Some of the problems on my home laptop from Windows 10 updates are pretty bad. And those updates happen whenever they want to do them despite any update times you have in your settings.
I could go on but essentially once data is out of your hands, you really don't have any control of that data. I'd be more likely to be more accepting of telemetry if I actually controlled what was sent to a vendor and it was a process of submitting telemetry data instead of them collecting and uploading the data.
Collection of data has just been misused (or abused) so much that I have a hard time with those things. All of it seems half baked.
But that's just me. You can find plenty of blogs, posts, explanations which state there are no vulnerabilities, it's anonymous/aggregated, it's important and beneficial for product improvement.
Sue
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply