My IT department does not believe it is necessay to have DYNSA as owner of the Dynamics database. What problems can I expect if this is not changed. Does DYNSa have to be owner of the databases.
*This post is locked for comments
Thank you for this post. We just encountered this very issue where companies were not populating the SY00100 table with the new company's information. We discovered our DYNAMICS database is owned by 'sa' instead of 'DYNSA'.
Although this is an old post but I hope it can help anyone who are searching for this
One of the issue is there will be error when creating company. Details as per link below to Microsoft Knowledge Base
support.microsoft.com/.../error-message-when-you-create-a-company-by-using-microsoft-dynamics-gp
If they are concerned about permissions you can explain that GP encrypts passwords so that users cannot directly access SQL.
See the Encryption section on David Musgrave's blog post.
blogs.msdn.com/.../why-does-microsoft-dynamics-gp-encrypt-passwords.aspx
Mike,
One issue I have personally seen is during upgrades. I have seen them fail when DYNSA is not the owner of all the GP databases (not just DYNAMICS, but the company databases, as well).
HI Mike,
Yes we required that DYNSA needs to be the owner of the databases. There isn't really a list of issues that you will run into but I can promise you will run into issues eventually. The link Donnette provided should give you some more information.
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
