March 21, 2018 at 7:01 am
Hi All, I have a plan in place for a up of our OLTP database from 2014 to 2017. It will be a separate upgrade-- meaning- the database will be restored to a newly build SQL server 2017.
I have few questions regarding this.
-- can a always -on be setup between a node of 2017 to 2014? let call this server A. I think it cant because you cant restore a higher version database to a lower version. looking for confirmation of this.
-- a separate BI system which is 2014 version. Lets call this server B this will not be upgraded to 2017 . Server B has a few SSIS packages which extract data from few of the tables from server A. will the SSIS be able to do the same after the upgrade of the OLTP database? Any thing needs to change in the package besides pointing it to the new upgrade version?
Many Thanks,
March 21, 2018 at 8:33 am
No idea about the SSIS.
Availability groups cannot be set up between different versions.
And please, test carefully before you upgrade production.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 21, 2018 at 9:28 am
GilaMonster - Wednesday, March 21, 2018 8:33 AMAvailability groups cannot be set up between different versions.
Gail, please correct me if I'm wrong here... but...
You can have two different versions in the same AG (aka upgrading the secondary before upgrading the primary)... The issue is that once you've failed over to the higher version you can no longer fail back to the lower version.
March 21, 2018 at 9:32 am
Jason A. Long - Wednesday, March 21, 2018 9:28 AMGail, please correct me if I'm wrong here... but...
You can have two different versions in the same AG (aka upgrading the secondary before upgrading the primary)... The issue is that once you've failed over to the higher version you can no longer fail back to the lower version.
Afaik both of the below statements are true.
You can have two versions in an AG as part of a rolling upgrade.
You cannot set up an AG with different versions.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 21, 2018 at 11:00 am
GilaMonster - Wednesday, March 21, 2018 9:32 AMJason A. Long - Wednesday, March 21, 2018 9:28 AMGail, please correct me if I'm wrong here... but...
You can have two different versions in the same AG (aka upgrading the secondary before upgrading the primary)... The issue is that once you've failed over to the higher version you can no longer fail back to the lower version.Afaik both of the below statements are true.
You can have two versions in an AG as part of a rolling upgrade.
You cannot set up an AG with different versions.
That's my understanding as well. Thank you for the confirmation/clarification.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply