> > You may legitimately need one really large table but most applications > > don't. > > The most common scenarios: > - get a single marker from subset of individuals > - get a subset of markers from a single individual > - get a subset of markers from a subset of individuals > > There is no "old" data one could get rid of (as in your example from sprint). >
Too bad. My guess is that you're doing the right thing trying to consolidate. It's going to take expensive hardware no matter what you end up doing. Your design is larger than any I've ever heard of using sqlite. My guess is that it will work if you have enough RAM. I've used much larger databases than this on all of the big commercial database engines (sqlserver, db2, informix, oracle). Any of them will certainly work for you.
