For an iDBA, predicting the future needs and expected growth of the database objects is crucial. During development and testing phases, the iDBA may have the luxury of making changes freely. It could be as simple a process as informing all the users of the database, finding a convenient time to perform object changes, and then making the changes even if it may require a restart of the database instance. Once the system goes into production, however, this luxury is immediately lost. If planning for object growth is not done properly, the iDBA can be placed in a very difficult position.