August 20, 2013 at 3:07 pm
PLATFORM: SQL 2008R2 Enterprise 64
Q: Outside vendor that provides our accounting software is requiring access to our database as the dbo user (the useer that is the database owner) to perform data changes directly as part of an upgrade. They say that no schema changes (no DDL commands) will occur but I'd rather they just not be able to execute any DDL commands (or DCl) anyway, limiting their access to DML command within the database.
SInce the actual dbo user is fixed and based on what I understand, not something you can change security/access wise, my thought was to create a user and make them a member of the db_owner role and then restrict their access so as to disable the ability to change the schema.
Thoughts? Is there a better way to do this, to provide db owner access for DML commnands only?
Thanks
Kindest Regards,
Just say No to Facebook!August 20, 2013 at 3:36 pm
I think you should first check your license agreement. If it says that upgrades require dbo access, you should give them dbo access. What if you call in a week later about a bug, and they find out that you tripped them and says "support contract voided, you will have to pay through the nose".
If you want to limit the access of the upgrade, you should not put them in db_owner at all, but only grant the permissions you think they need.
And you may get away with it this time, but next time, the vendor may actually want to make changes to the schema.
Full disclosure: my main client is a vendor, so I am that side of the fence.
[font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply