Re: data modeling conundrum

Thanks for the info!
> Let me clarify the nature of the data...

These number pairs are x,y coordinates of a 2-D plot (i.e. intensity vs.time). So, the parent record is a chemical compound and the x,y coord. are the resulting data from an analysis of that compound.

Applications will query the database for a set of compounds and the associated x,y coord. data. Generally, the query will be for 200-1000 compounds at a time (which would be 200*400 or 1000*400 rows if a child table was created for x,y data! which seems like too many rows to query quickly, i.e ~10-20seconds.) The appl will store the contents of the cursor/recordset in a datastructure and recreate the plots when say, the user clicks on a sketch of the compound. Having a child table for the x, y data would be a more elegant way to store the data, but considering the the growth rate 100,000*400 rows/year. Yeeks! And the average rows queried from the application each time would be 8000 to 40,000 rows I am a little reluctant to take this path. Maybe this plot should created and processed into picture file (.EMF or GIF or something), then stored as a blob in the database or out on a network???

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Fri Nov 17 2000 - 10:01:30 CST