Re: Database Size Vs System Performance

Thanks,
   Scott


Wilt, Charles wrote:

 And let me answer it in a slightly different way.

 Why exactly would the DB need to "watch" anything?

 Nothing can happen, open/close/read/write/update/delete/ect, that the
 DB isn't involved in. Thus, it doesn't need to "watch" anything.
 The DB will maintain the objects as they are used.

 The only difference you'll see besides the extra DASD us will come
 from an increase in the number of objects in use. For example, say
 you've got 10 people using the same object in the current test
 library. With the new setup, you might have 4 people using the test
 object, 3 using the development object and 3 using the training
 object. So now instead of 1 active object, you've got 3.

 Unless you have a huge development staff which currently work on the
 same stuff at the same time and will now start working on different
 things, the difference will be nothing to worry about.

 In other words, 10 people working with 10 test objects will not be
 any different than 4 people working on 4 test objects, 3 people
 working on 3 development objects and 3 people working on 3 training
 objects.


 HTH,


 Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi
 Electric Automotive America ph: 513-573-4343 fax: 513-398-1121