SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Securing a dbo User in SQL 2008 R2


Securing a dbo User in SQL 2008 R2

Author
Message
YSLGuru
YSLGuru
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4458 Visits: 1667
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!
Erland Sommarskog
Erland Sommarskog
SSCertifiable
SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)

Group: General Forum Members
Points: 5254 Visits: 875
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.

Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search