1.Database gets full, which can cause bigger problems: application crash, data loss etc.

2.Hard disk is getting full and its not monitored for that.

3.Network disconnects combined with lack of resuming functionality: for example downloading a large application that takes time is interrupted.

4.Memory crash.

5.Power off – electricity down, hardware getting old, processor heating etc.

6.As a problem of long duration I am listing software getting old – because it can affect the business and a bug is something that reduces the value of the application.

7.Competition may appear that creates the need of better software and reduces the current one.

8.Software can become obsolete – there is no practical need for it anymore.

9.Software becomes incapable of satisfying the needs of  increasing number of users.

10.Lots of issues that couldn’t be predicted in design process.

ShareThis

1. Richard Hill says:

   November 5, 2010 at 8:05 am

   Look for databases getting fragmented across disk segments where are the dbspaces going to find there chunks of data . As data is added the extents may become dispersed across different disk sectors.

   Check the DBA has a fragmentation strategy.

   Reply to this Comment
2. Eusebiu Blindu says:

   November 6, 2010 at 9:21 pm

   Hi Richard
   Thanks for commenting and adding a a good tip.

   Reply to this Comment
3. jioni says:

   May 30, 2012 at 1:40 pm

   not sure if what you are detailing here appears in a CI Environment. cause there i think that you couldn’t have some of the possible bugs. just wondering if this is applicable for those envs or this is applicable only for a client based env.
   indeed the DBA has a fragmentation strategy – this is a good point. not sure regarding the network probs

   Reply to this Comment