Entire access database size: 2,972 KB

5 tables total 2 major tables, with rows x cols of 24×37 and 29×600

New data is added when new faculty members come to the Graduate School. Old / expired faculty may be removed also. The growth pattern of the data depends on the growth of the University, but the data will most likely stay relatively small for a long period of time.

1-2 users. Me and my IT helper.

2-4 users. One office that has ~5 workers will actually need to change the data.

‘www.umbc’ webserver user. This is the important one here. We would like to create a webpage that queries the database live via PHP to display up to date faculty information. Our current page ( http://webdev.umbc.edu/grad_list/index.html ) is updated manually. We could implement the code in two ways that would effect the number of read access’s on the database. A) the code queries and updates the listing once a week. B) the code queries and updates the listing everytime someone accesses the webpage. The entire Graduate School community uses this listing. I am unable to get statistics from OIT to tell you how many accesses occur to this page. We get about 2 requests per month from programs to update it.

click picture to zoom

Same as phase 1. Will be measureable by size of temporary Oracle table space.

~6 tables total Same data, just normalized into different related tables

Same as phase 1.

Same as phase 1.

Same as phase 1.

Same as phase 1. We would slightly alter the PHP code to query the same data correctly.

click picture to zoom