Post reply

Upgrade From SQL 2012 to SQL 2016 - Problem with Certificates

  • July 22, 2018 at 9:58 pm

    #354679

    Comments posted to this topic are about the item Upgrade From SQL 2012 to SQL 2016 - Problem with Certificates

  • July 22, 2018 at 11:22 pm

    #1998550

    Hi Mike,

    Thanks for the Article..

    Could you please provide some scripts for the steps you have provided which would help us to test.

    Thanks in Advance..!

    Regards,
    AG

  • July 23, 2018 at 7:31 am

    #1998588

    I use certs extensively, so this is definitely good information to know.

    Be still, and know that I am God - Psalm 46:10

  • July 23, 2018 at 7:43 am

    #1998591

    This is the good stuff.  This is a great article about something that you will only find out about by working in the field.  Thanks for writing the article.
    Jeff Bennett
    St. Louis, MO

  • July 23, 2018 at 11:40 am

    #1998651

    Could be the same case migrating some dbs from 2014 to 2017?

  • July 23, 2018 at 11:46 am

    #1998652

    Thanks for the feedback.

    Fernando Jacinto Alvarez: I don't know, recommend you test this

    aswini.gangaraju: yeah, I should have done this before, just so tedious. Not sure how to attach to the article, so attaching them to this post.

  • July 23, 2018 at 11:48 am

    #1998653

    User error, attach failed, trying again

  • March 15, 2022 at 3:54 am

    #3999504

    Hi Mike,

    article was very useful i have hit the same issue now migrating SQL server from 2012 to 2016 with DQS upgrade, can you provide the solution in more detail

    find and drop all associated signatures from related stored procedures

    drop the users that we'd created from the cert

    drop and then recreate the cert

    re-create users from the cert

    re-grant rights to those users

    re-sign all the stored procedures that need signing

     

    Regards,

    Lakshan

Viewing 8 posts - 1 through 7 (of 7 total)

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