Dynamics Community Forum Thread Details

Impact of disabling DNYSA

We have a client being audited by the world's most annoying auditors. They now want to disable DYNSA. DYNSA is the owner of all the GP databases. What would be the impact of disabling DYNSA?

The biggest issue we usually see regarding DYNSA is when DYNSA isn't the db owner for the GP databases, specifically the system database and creating new company databases.

During the creation of the company database, GP Utilities gives access to the new company to the 'sa' login and then the db owner of the system database, which should be DYNSA.

If, for example, 'sa' is also the db owner, then it attempts to give access to the company twice, to 'sa', which results in a primary key error on the SY60100 table.

This is just one of the examples I can think of offhand, but it wouldn't necessarily prevent you from disabling DYNSA.

The SecurityPlanning.pdf also mentions:

"The database owner is set to DYNSA for every Microsoft Dynamics GP database. It is essential that DYNSA continue to be the owner of every Microsoft Dynamics GP database. If a different owner is assigned, complications can arise when deleting user accounts and granting access to companies. "

It also mentions during upgrades, that:

" When the system administrator (“sa”) logs into Microsoft Dynamics GP Utilities, the application checks to see if the password for DYNSA is either <blank> or ACCESS. If either of these is true, the user must enter a new DYNSA password before continuing with the upgrade."

.........so, it may be looking for DYNSA behinds the scenes when launching Utilities, though I can't say I've ever had Utilities prompt for DYNSA or the DYNSA password when running an upgrade.

Thanks

Quick Links

Leaderboard