Andrew

We already archive information by taking it from the active table and dumping it into a text file so that it can be retrieved later - but this was tooooo complicated to restore it, and report on it, hence the need to store more. Splitting the table is a good idea - something that I can work on...

As far as the WI are concerned - I'd bet on a 5-0 result more than changing this stuff to SQL...perhaps they should get Sir Viv back on board - at least he got SOME runs this afternoon. Lets hoping Sydney puts on some good weather for the Syd-Hobart as we'll actually be in Sydernee to watch!

Thanks again

Cheers

Chris

Thanks for the help



>Hi Chris,
>
>AFAIK, there's no way to make VFP store > 2GB in a table. As for breaking up the table, you have several options.
>
>

Partition the table vertically - that is make it two (or more) tables with a one-to-one relationship between them. Move some of the columns to another table and relate the new tables using the existing primary key.
>

Partition the table horizontally. Make tables that break up the data into (say) rows with customer IDs between 1 and 10000, 10001 and 20000, and so on, or customers with a company name starting with the letters A-F, G-M, N-R, S-Z (or whatever)
>

Periodically sumarise and archive rows from the table. For example, each month extract all of the information that's > 3 months old. Create a summary table if required for day-to-day reporting purposes and store the old information in archive tables.
>
>Each of these approaches requires different changes to your app. The third approach only requires changes to the data retrieval and maintenance components (data entry continues unchanged) while the other two probably need changes to data entry as well. However, the first two approaches leave all of the data available.
>
>I've not addressed the SQL Server vs VFP question here. It may indeed be worth considering upsizing the data to SQL server - I'm not really in a position to make that judgement though from the information you've provided.
>
>Have a great holiday season, and here's hoping for a 5-0 series against the WI!
>
>Cheers,
>
>Andrew
>
>>Hi all
>>
>>One of our customers recently reached the table size limit on one of their tables (2gb i think) and asked if we would consider changing our VFP stuff to SQL. I'm somewhat reluctant to do this as I'd prefer to solve the problem using VFP which I am more familiar with.
>>
>>Does anyone know if VFP tables can store more than 2gb somehow - or perhaps know of any way we can automatically use a new table when the file size gets close to 2gb.
>>
>>Thanks in advance
>>
>>Chris Kable