You have different people designing different systems. How them use the nomenclature is going to be based on their experience and their jargon. Language is always going to be an issue. For instance:

"I've got to go TDY to 7-level school for my AFSC at Keesler. Hopefully I'll do well enough to be DG."

If I carried that conversation with another US Air Force person, they'd understand in a second what I was saying. If I stepped across and carried that same conversation with say a member of the Marine Corps, they'd understand TDY and Keesler, but they might not understand 7-level school, AFSC, or DG. Now, if I had that same conversation with someone who hadn't ever been in the military, they probably wouldn't understand anything I just said except maybe Keesler. We all use jargon, whether or not we realize it or not.

Another example:

"The developer had dbo rights and managed to drop the tables. Get with the sysadmin to pull the backup tape for the server. We need to grab the full and the differential and perform a restore back to 2 days ago. You're going to need to send out an email to all the developers telling them to stay out of the db because we'll have to put it in single-user mode until we're done."

To the DBA, that should all make sense. But even to a system administrator, some of that may be incomprehensible. Now, imagine you were Joe Blow on the streets. Talk about dropping tables probably has a totally different connotation than for the DBA.

But it all boils down to this:

GRANT = I give you permissions.

DENY = I explicitly deny you permissions.

REVOKE = I undo any grant or deny I may have previously issued.

K. Brian Kelley

http://www.truthsolutions.com/

Author: Start to Finish Guide to SQL Server Performance Monitoring

http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1