+ 0 Votes You could just show them robo_dev April 10, 2013 at 4:12am PST Login as a regular user and try to change the table, and see the error message. Pushing a table to another server could create problems, like the fact that the audit process stops working when the other server goes offline for maintenance. You could have the database logging level turned up all the way, and send the logs to a server that only your security team has admin access to. That's the only way to ensure that somebody with elevated access (like your DBAs) do not make changes and then can cover their tracks. If the permissions are set properly in the table, simply show them that the permissions are set properly; they could validate that by logging on as a limited user and trying to change that table. If it's set properly, they will not be able to do that.