Post reply

Always On issue after SP2 CU3 or 4

  • March 5, 2015 at 10:22 am

    #398126

    I'm trying to get SP2 rolled out to production, but started in QA with SP2 CU3. Then I read about this issue. We aren't currently using Always On Availability Groups, but wanted to put a clean upgrade on production.

    I heard CU5 would come out this month. Any word on that?

  • March 5, 2015 at 12:24 pm

    #1782016

    I would suggest you to have a look at this link

    For the release of the CU5 for SQL Server 2012 SP2 , the release date ( according the same post ) is end of March 2015.

    An advice from the SQL Server Support Center : to avoid to install isolated CU and to prefer to wait for the release of the next SP ( as the Support is doing full tests for a new Service pack , it is not the same thing for a CU for which the tests are done less heavily , except to search incompatibilities between the KBs included in the CU ). It is why sometimes , some KB included in the last CUs are not included in a new SP.

    At the end of the article , you should find

    SQL Server 2012 RTM or Service Pack 1 are not affected by this problem

    ( about the problem of the databases participating to AlwaysOn Availability Groups (aka AG), the AG might be reported as NOT SYNCHRONIZING )

    Don't forget to read the comments at the end of the article.

    I hope that I have been understandable despite my poor English language.

  • March 5, 2015 at 12:30 pm

    #1782019

    Thanks. Sounds like if I do anything in production it should just be SP2 with no Cumulative Updates. I hear your concern about CU's but seems I read another article that made it less desirable to skip everything between service packs.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply