January 11, 2017 at 9:24 am
I think our server's OS is not compatible with the Upgrade Advisor. I think the minimum OS is Windows Server 2008 R2 (mistakenly typed SQL2008 R2 originally), but we're on R1.
Suggestions ?
Edit.. Fixed OS info... I Basically FUBARed this thread... never mind.
January 11, 2017 at 9:33 am
homebrew01 (1/11/2017)
I think our server's OS is not compatible with the Upgrade Advisor. I think the minimum OS is SQL2008 R2, but we're on R1.Suggestions ?
Based on this doc, you should be able to upgrade, as long as you're on 2008 SP3.
SQL Server is an RDBMS, not an OS.
January 11, 2017 at 11:37 am
Sorry, I wasn't clear. Our Operating System seems to be just short of compatible with the Upgrade Adviser tool.
I want to run the tool to look for "BreakingChanges" etc ahead before the actual upgrade.
January 11, 2017 at 11:48 am
homebrew01 (1/11/2017)
Sorry, I wasn't clear. Our Operating System seems to be just short of compatible with the Upgrade Adviser tool.I want to run the tool to look for "BreakingChanges" etc ahead before the actual upgrade.
I'm not sure what suggestions you are hoping for.
At risk of stating the bleeding obvious:
1) Upgrade your o/s, or
2) Restore a copy of your databases onto a machine with a newer o/s, or
3) Do without the upgrade advisor
January 11, 2017 at 11:52 am
I was just hoping there was an earlier version of Upgrade Adviser that works with older OS... that maybe I missed in my search.
Since people upgrading SQL are likely to be on old machines, seems odd the tool only works on newer Operating Systems.
Oh well
January 11, 2017 at 12:17 pm
homebrew01 (1/11/2017)
I was just hoping there was an earlier version of Upgrade Adviser that works with older OS... that maybe I missed in my search.Since people upgrading SQL are likely to be on old machines, seems odd the tool only works on newer Operating Systems.
Oh well
As you have not specified which o/s you are talking about, I can offer suggestions only in a generic fashion.
Any 'earlier version' of the UA is, presumably, not going to be for SQL Server 2016. Otherwise, it wouldn't be earlier. Once again, I find myself stating the obvious.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply