Steve Jones - SSC Editor wrote:
What do you mean, Neil? The question states the data is encrypted in 2016, moved to 2017. There's no "up to date" here. The algorithm changes. You can't xfer a symmetric key. You create it, because they are supposed to be deterministic. However, the algorithm changed for the hashing of the salt in 2017 as the default, so the key isn't symmetric.
I meant the issue to which Sue referred. I'd found that the algorithm had changed between the years but then saw the references to the CU which fixed it. The link below suggested it could be done, if the CU was applied. As I said, the usual assumption is that the servers in question are up to date with CU's, so I went with the answer I did. I was then a bit surprised to see that the answer was that it couldn't be done so I was wondering what I'd missed. I do accept my pre-caffeine tone was a little snippy, and for that, I apologise.
On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" ... I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
—Charles Babbage, Passages from the Life of a Philosopher
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537