Upgrade From SQL 2012 to SQL 2016 - Problem with Certificates

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

  • 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..!


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

    [font="Tahoma"]Personal blog relating fishing to database administration:[/font]

    [font="Comic Sans MS"]https://davegugg.wordpress.com[/url]/[/font]

  • 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

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

  • 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.

  • User error, attach failed, trying again

  • 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




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

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