I would recommend a direct RELOAD <newname> rather than unload/reload, because the UNLOAD creates a text file that can be read by anyone at all, no matter what the database passwords are, and includes the owner password. When the UNLOAD/RELOAD must be performed, then either the developer of the owner must do it, remembering to destroy the text files when done.
1. Give the owner password to one or two other trusted employees who can then do the unload/reload 2. GRANT ALL PRIVILEGES to one or two trusted employees, retaining the OWNER password for the developer and the owner. This allows the owner to remove access for the employees if they leave or whatever. > > >>Hi all, > > � Does anyone have some good advice on the topic of Database >Ownership. �We just recently took our PUBLIC 'ly owned database, but now >the company owner would like to be able to restrict access to one of the >tables. � I Set him as OWNER, and Granted access (table by table) to the >users. �Now... unload/reloads can't be done by anyone but the owner? > � How do we set it back to public till we figure a better way to do this? >Thanks, >Dan > > > > >Dan Champion >P.O. Box 223 >Grandville, MI. 49428-0223 >www.championsolutions.net > > -- Albert Berry Full Time Consultant to PSD Solutions 350 West Hubbard, Suite 210 Chicago, IL 60610 312-828-9253 Ext. 32 __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
