True. With MS sooner or later you will have to do a security update (or be stuck with an insecure system), and chances are that there will be a EULA that will conflict with your company's (privacy) policy.
I'm currently working on a database project which will contain very privacy-sensitive (medical) data. We chose for postgresql (not to start an mysql pg flamewar, but pg was the more suitable for our purposes) because it's open, and thus safer. We would never trust this data to be stored in a database made by a company that will possibly break into the data.
Of course, MS (and Oracle and the rest) will say that they would never do such a thing, but that's beside the point. Once I agree to the EULA they have the _right_ to do it. And even if the current EULA looks OK, there is no guarantee that future ones will be OK.
Slashdot Mirror
True. With MS sooner or later you will have to do a security update (or be stuck with an insecure system), and chances are that there will be a EULA that will conflict with your company's (privacy) policy. I'm currently working on a database project which will contain very privacy-sensitive (medical) data. We chose for postgresql (not to start an mysql pg flamewar, but pg was the more suitable for our purposes) because it's open, and thus safer. We would never trust this data to be stored in a database made by a company that will possibly break into the data. Of course, MS (and Oracle and the rest) will say that they would never do such a thing, but that's beside the point. Once I agree to the EULA they have the _right_ to do it. And even if the current EULA looks OK, there is no guarantee that future ones will be OK.