The Ten Commandments of Oracle DBA

II. Thou shalt not allow the Storage Clause to default, for thou shouldst know where and how thy data is stored.

III. Thou shalt not allow the Tablespace name to default, nor shalt thou place a Table in the same Tablespace as its Indexes, Primary Key Constraints, and Unique Constraints, for this is an abomination to the DBA.

IV. Thou shalt not hard code a username or password into an application, for this violates the sacred security of the database.

V. Thou shalt rebuild thy indexes from time to time, for this will reduce storage requirements, and improve performance.

VI. Thou shalt not maketh the client to do the work of the server, nor the server the work of the client.

VII. Thou shalt grant privileges on thy Database Objects through Roles whenever possible, for this will simplify grant administration.

VIII. Thou shalt use Constraints, Triggers, and Declarative Integrity wherever possible, for this will protect thy data from people who know not what they do.

IX. Thou shalt name thy Constraints, lest Oracle give them names that are void and meaningless.

X. Thou shalt covet thy neighbor's Common Code Table, his Commonly Used Procedure, and anything and everything that has already been invented, and shalt share thine own good stuff too.

We love hearing from friends via the 'net...so e-mail us
You can sign our guestbook You can view our guestbook