July 3, 2018 at 2:25 am
I have a SQL Server 2008 R2 installation that I'm planning to upgrade to 2017, it's a supported path so I figured this would be the most hassle-free way of getting there.
As part of my due diligence, I had my IT department create a snapshot of the server for me to run through the upgrade process to test for any gotchas and pitfalls. It didn't take me long to find one, we haven't purchased the licence yet, but I figured I'd be able to test an upgrade from 2008r2 standard to 2017 developer. I figured wrong.
I don't deal with the purchasing and licensing side of things so apologies if this is a dumb question, but do you know if it's reasonable to ask MS for a temporary 2017 standard product key.
Otherwise, do any of you have any suggestions for a way around this little peccadillo, other than a parallel install and migrate, that is?
Thanks in advance.
July 10, 2018 at 12:59 am
This was removed by the editor as SPAM
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply