i'm learning... and it's called work...

build a page, to show records filtered with "data status date"

the caveats:

-there would be 5k+ records to show.

-the data is sitting on single database with 2k+ tables,

tables are prefixed w/ application name i.e "INVENTORY_*", "PAYROLL_*".

-there are 20+ applications that'd be accessing the db at any point in time.

-some of the 20+ apps have a normalized table structure & some have not.

-app and db are sitting on one machine & it's a P3, vintage servers

the solution:

-use sql paging, to show specified number of records per page; basically split the data into subsets.

-recomend more specific filter options i.e. field range, dept, item category, etc.

-use indexes on queries.

on the solution part, item 3 is within our control... we can do this easily but the first 2 items are the catch. the stakeholder wants to be able to view all the data as filtered only by the data status date. no other filters would be created. does not want to do a paging function coz, it's better to scroll down rather then click thru the page numbers. would also need to edit a selected row within the page's tabular data presentation. and requires it to be fast. this requirement would work well on a desktop app, it's a challenge if it were a web app...

i do believe that the paging solution plus the additional filter options would really be able to aleviate the perfomance issue here, i've recomemded this approach over and over again and i'm still recomending this (else, i won't be blogging about this).

this are one of the things i do... i'm learning... and it's called work...