thanks Michael Ross, I forgot about the DBA. I didn't think about that one, since we don't have one:-D
But the reactions exactly draw out what I mean. To technical! Having 100 rows of data is in about 80% (or more) of the times to much info. Users are interested in data they can use. Overviews are reports and charts, not in a 'normal' screen. Most of the times, the user wants quick, accurate and easy to read data. As one of the reactions mentions the search. Look into these kind of functionalities. Is it useful? Does is benefit the user?
A programmers (designers) task is not to build what the user wants, but what the user needs. Most of the time the perception of the users of their needs is wrong and based on worst case scenarios. Never ever ever ever cater for worst case scenarios, this will only lead to an unworkable system which is great in 0.5% of the times.
Take a step back, look at what the system is doing, what is needed for the user to perform his/her task.
Take this approach, look at both the functional and technical sides of the stories. This is the task for a developer. If not, you are a typist and no more.