If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.
The only things I can think of:
- do not grant db2 access to "alive" users
- only grant db2 access to "task" users and do not share the passwords
- capture all housekeeping in scripts and grant execute rights by means of sudo
- use static SQL only (if possible)
- client application (really need their password) are only permitted to execute static SQL or only update the DB by means of Stored Procedures.
- applications only access userviews, no real tables. This gives you the most control by means of triggers on tables, and "instead of" triggers on views.
- do not expect to be liked by your IT collegues
I am looking for a best practise document which will be a standard in case of any activity like installation, backup and recovery.
For eg : Logretain should be on.......
I am looking for a best practise document which will be a standard in case of any activity like installation, backup and recovery.
For eg : Logretain should be on.......
I would check out the lazydba forum.
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390