Re: Choosing a database for a large amount of data

First, forget about MS Access - for this much data, you need a 'real' RDBMS.
Second, forget about MS Access - for the web you need something net standard, small footprint and fast - consider Inprise InterBase. Third, forget about MS Excel - you limit your clients and your servers and you take extra time passing data around. Use standard SQL to get the results and drop them into a JavaBean to do the chart drawing directly for you.
Fourth, consider using pre-built queries (and pre-run ones) for the most common and least changing data. It will speed up overall response times. For the rest, use a 'waiting' page to show the user something is happening - it makes it seem as if things are moving faster.

On Wed, 14 Jun 2000 17:11:31 +1000, "Demetrio Trombi" <D.Trombi_at_pgrad.unimelb.edu.au> wrote:

>I was wondering whether some of your more experienced folk might point me in
>the right direction. I have constructed a large database with stock market
>information that I use to import into Excel with its charting functions. At
>present I use MS- Access and have over 90,000 records with 7 fields -
>Processed file ID, Company Code, Open, High, Low, Close, Volume. This is for
>approx 1.5 years of history and my goal is to have around 10 years. Already
>though, querying this database takes several seconds and it has occurred to
>me that there must be a more efficient way as I have noticed that even over
>the internet I can get web pages to display charts quicker than I can. And
>as, in the future, the database will get larger and larger this will only
>make things slower. I have tried to create a different tables in the same
>database that represents each company but this really didn't do much. What
>do you think? Perhaps another type of database or another system. I'm not
>very experienced with the different type of packages available so please any
>info. will help.

-- 
Mark A Preston BSc, FIAP
The Magpie's Nest
mark_at_mpreston.demon.co.uk