Occasionally I create views or tables in our Visual Manufacturing Database, and as expected, I need to manually set the permissions on the sql object to allow users to be able to access them.
However, I am noticing that when I look at past sql objects that I created, and examine the permission settings, I can see that ALL of my Visual Manufacturing users have "Select" permissions on the sql objects that I created. When I set the permissions manually, I only gave permission for a subset of users.
How does this happen? I checked nightly Maintenance Plans, and Scheduled SQL Server Agent jobs, but I don't see anything that could be automatically creating permissions for the users that I did not create.
Is there anything in SQL or the Visual Manufacturing application that would query for new sql objects, and give the Visual Manufacturing users "Select" access to them?
In Visual Manufacturing, the application creates two sql users when creating a new user. The named user gets "Select" access to each sql object. The second user, called the "blind user" ({username}#) gets "Delete", "Insert", "Update", and "Select" access to each Table in the VMFG database.
Something is setting these permissions, but I can't tell what it is.
Can anyone familiar with VMFG and / or SQL Server shed some light on what might be happening.
Thanks in advance for your insight.
Regards,
John Keegan
