question

Can you please suggest few of the techniques/procedures that we should do on database to run the system without any harm and to save from danger situations and to identify it before as like prior intimation? It's not limited only to the performance. What I really worried is, we are working with really very large database systems and few days back we identified that one of the table's identity column value is very close to reach the max value of that data type, it's almost like if we don't identify this issue, damn sure within 6 months the table will give overflow error and the system will be broken and it can't be solved immediately since this table identity column is used in more than 3000 stored procedures. Just think once if we don't identify this issue, the loss will be huge even the total application systems will stop working which are pointed to this table. Then after I have implemented a script to monitor the identity columns and calculating the expected run out date. These are the ones that I’m more worried about actually. Things that could cause an outage. Just I want to know these type of very dangerous checklists to protect my database system from huge loss. Now, really what I want to do is, to have an eye on this kind of problems. Could you please let me know on what areas really we should monitor to avoid the horrible problems/situations on database? Just I want to know these type of very dangerous checklists to protect my database system from huge loss. Please help me on this.