Skip to main content

Notifications

Finance | Project Operations, Human Resources, ...
Suggested answer

Great Plains 2013 Password Encryption and SQL High Availability

(0) ShareShare
ReportReport
Posted on by 5

I have a customer running GP 2013  using native password encryption.  They are concerned about GP and SQL high availability.  What options are available?  What if they want to take advantage of SQL FCI or Availability Groups?  Is this possible?

Categories:
  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,021 Super User 2024 Season 1 on at
    RE: Great Plains 2013 Password Encryption and SQL High Availability

    I've never tested it in a Clustered environment, but technically yes.

    See this post to get the details: community.dynamics.com/.../dynamics-gp-on-a-cluster-environment

    The first link in the above post is broken and here is the correct one :

    support.microsoft.com/.../description-of-the-requirements-to-run-replication-clustering-log-ship

    This community post has an official response from Microsoft :

    community.dynamics.com/.../high-availability-with-gp-2016

    Hope this helps.

  • scientificruler Profile Picture
    scientificruler 5 on at
    RE: Great Plains 2013 Password Encryption and SQL High Availability

    Thanks Beat.

    So are you saying it is possible to get an FCI to work?  Generally SQL clusters are accessed via the "listner" name which is defined in DNS for the exact purpose you mention.   Is this what you are referring to?

  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,021 Super User 2024 Season 1 on at
    RE: Great Plains 2013 Password Encryption and SQL High Availability

    Hi

    Microsoft has posted once a document about this topic and Dynamics GP doesn't support HA for SQL servers.. you can use transaction log shipping, but that's about it.

    If you do a search on the internet, you should be able to find the related papers about it I guess.

    Reason why this isn't supported lies within the way the user pwd is encrypted on the SQL server side from the GP client. It is based on the server's instance name in the ODBC entry.  Using another server with a different name would possibly fail authentication for all users, except 'sa'.

    One way I had solved this problem was to use a DNS 'Alias' entry for the GP SQL server.. (i.e. DYNAMICSGP).

    This way if you ever had to switch from one SQL server to the other, the name would remain identical and the passwords would still work. This requires careful planning, but works fine.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Announcing Category Subscriptions!

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Verified Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,359 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,370 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans