InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 14:41:16 GMT20http://www.sqlservercentral.com/Forums/Topic848304-359-1.aspxIt is a risk if you have someone that wants to be milicious, he can steel information or remove important data that will cost you time and man hours to fix. There is another way to protect the system and you can do it with server triggers. This will allow you to grant db_owner rights to users that log in from the app and deny access if they log in with anything else.Mon, 18 Jan 2010 05:10:26 GMTOomBoomhttp://www.sqlservercentral.com/Forums/Topic848304-359-1.aspxIt is a risk to give db_owner permissions to a user. check this link: [url]http://technet.microsoft.com/en-us/library/cc966507.aspx[/url].Sun, 17 Jan 2010 04:00:15 GMTIgnacio A. Salom Rangelhttp://www.sqlservercentral.com/Forums/Topic848304-359-1.aspxWe are using a VB6 application thru Citrix Metaframe 4 on Windows 2003Servers that accesses a database on an SQL 2005 server (Windows Server2003 OS) that requires that the users (or user group) have theDB_Owner Database Role Membership Permission in SQL 2005. A client isconcerned that this level of access for their users will leave openpotential security risks. When we remove the DB_Owner Database RoleMembership Permission in SQL 2005 our VB6 application cannot properlyrun stored procedures among other tasks. We use windows integratedsecurity (active directory) only setup and NOT SQL Serverauthentication.Is the DB_Owner Database Role Membership Permission in SQL 2005 a realrisk for security? The client is concerned the users can hack in anddrop or alter the databases.Thank you!Fri, 15 Jan 2010 08:13:44 GMTbirdman357