This is an excerpt from the book "Oracle DBA Checklists Pocket Reference" published by O'Reilly. You can purchase the book here.
Follow this checklist to make sure your application schemas are ready to be
- Perform physical configuration:
- Does each application have its own schema?
- Does each schema have its own set of table and index tablespaces?
- Are tables and their corresponding indexes in separate tablespaces?
- Check on performance issues:
- If you are implementing referential integrity, are all core foreign keys indexed?
- Are there tables without indexes?
- Are there tables with too many indexes?
- Are there tables with similar indexes?
- Are the schema objects regularly analyzed?
- Check on security issues:
- Are all object grants performed through roles? (While doing this is not strictly necessary, it does make administration much easier.)
- If your applications allow for it, are all updating capabilities granted through nondefault roles?
- Check on miscellaneous issues:
- Are naming conventions in place for all database objects? (While using consistent naming conventions is not strictly necessary, it does make administration much easier.)
- Is the value of the PCTINCREASE parameter for each tablespace greater than 0? This will ensure the automatic coalescing of free space. If you do not want your extent sizes to change, you'll want to ensure that PCTINCREASE is set to 0.
For More Information
- Feedback: E-mail the editor with your thoughts about this tip.
- More tips: Hundreds of free Oracle tips and scripts.
- Tip contest: Have an Oracle tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize -- submit your tip today!
- Ask the Experts: Our SQL, database design, Oracle, SQL Server, DB2, metadata, and data warehousing gurus are waiting to answer your toughest questions.
- Forums: Ask your technical Oracle questions--or help out your peers by answering them--in our active forums.
- Best Web Links: Oracle tips, tutorials, and scripts from around the Web.
This was first published in June 2003