Open Forum

Expand all | Collapse all

Is DYNSA necessary?

  • 1.  Is DYNSA necessary?

    Posted Jun 03, 2019 08:51 AM
    We currently run GP2013R2. Yes, I know we need to upgrade.
    I always use "sa" for GP upgrade and other maintenance.
    I have never used DYNSA for anything.

    Is there any reason I need to have the DYNSA user? Would anything fail it I deleted it?

    If I delete it, can I re-create it later if we decide we want it?

    Thanks for you help.

    Bret Miller
    IT Manager
    Grace Communion International
    Charlotte NC

  • 2.  RE: Is DYNSA necessary?

    Posted Jun 03, 2019 10:13 AM
    Hi @Bret Miller

    Here is an article that may have the answer for you.



  • 3.  RE: Is DYNSA necessary?

    Posted Jun 03, 2019 10:34 AM
    Hi @Bret Miller,
    The referenced blog article by @Jo deRuiter is the first good reason not to get rid of DYNSA..  But sometime, and this happens more often then any DBA wants it, the databases are belonging to someone else (like a domain Admin or another domain user,or 'sa') because they were restored under that account and the person that did perform the restore didn't pay attention to select the proper owner of the DB at the restore time..
    SQL by default will assign the 'dbo' to the person that performs the restore.. So here you are with a a full Dynamics GP setup that was restored to another system (or on the original server after a crash) and DYNSA isn't the owner of it. Simple fix provided by Mariano Gomez at the end of his blog post..
    An other excellent tool would be the GP Powertools (aka GPPT) that has a nice utility called 'Database Validation' and that would check for you all the default security for your GP instance.
    That option allows you to return the right ownership to the GP Databases in case they are not, and also re-create magically all the SQL user accounts that are listed in SY01400 to be assigned to each GP company where they have security access to.​​ GPPT even allows you to completely reset all the user passwords in one shot and mail them out to the end-users if their e-mail address is linked to their respective GP account.  Talk about some headache savings when you have hundreds of users to reset.

    Beat Bucher
    Business Analyst, Dynamics GP SME
    Montreal QC/Canada
    Montreal QC GPUG Chapter Leader
    MBS MVP (2015-2018)
    All-Star 2013

  • 4.  RE: Is DYNSA necessary?

    Posted Jun 04, 2019 02:45 AM
    Thanks @Beat Bucher for the recommendation of GP Power Tools.

    The DYNSA user is meant to be the owner of the GP databases.  The password for this ​user is encrypted and so it cannot be used outside of the GP application. I know that runing some functions when DYNSA is not the owner of the databases can cause issues.

    I would say that yes DYNSA is required.



    David Musgrave MVP, GPUG All-Star

    Managing Director
    Winthrop Development Consultants

    Perth, Western Australia

  • 5.  RE: Is DYNSA necessary?

    Posted Jun 04, 2019 12:28 PM
    sa is the SQL Server System Administrator; DYNSA is the Dynamics System Administrator.

    You should never use the sa account for administering Dynamics GP unless there is no other alternative. There are four times I can think of when this is the case:
    1. Installing GP for the first time.
    2. Migrating GP to a new server.
    3. Using some of the PSTL functions which impact the database and mandate the use of sa.
    4. Installing/upgrading ISV products which require the use of sa.
    Everything else should be done using DYNSA ot a correctly configured GP user account (such as maintaining security).

    Ian Grieve
    Lead ERP Consultant
    ISC Software Solutions
    St. Ives, Cambridgeshire

If you've found this thread useful, dive deeper into User Group community content by role