I had some bad expierences with MySQL. I dont know if it was just me but, I was unable to perform a join operation. This immediatly caused me to ditch it.

I would definatly suggest using a sql server. It was bulit just for your situation. Although it is a little pricy by worth it im my opinion.

MS SQL Server can support 8,060 bytes per row and a table size of 32 Terabyes. (I think, correct me if im wrong)

And it works perfectly with fox pro.

If you cant afford MS SQL Server, I would suggest a free sql server. Check out Postgre SQL server, its a pain to set up and it dosent have an pretty GUI but it works, how well, im not sure. We only used one for testing, and didnt do anything other than some simple selects with no more the 2 people connected to it at the same time.

HTH
Eric



>Hi Craig,
>Appreciate your reply.
>
>>How about splitting the master table into multiple tables?
>That's what I meant by normalizing. Have nothing that even comes close that I can use as an index. Plus I have dupe records with only different dates (needed)
>
>>If your scan is taking that long, you don't have it optimized.
>I agree on that point. Need to work out what I could use.
>
>>You can't do a scan on SQL Server, so you may have to rearchitect your application. Everything in SQL Server is done with SQL statements.
>Thanks for that bit of info. Didn't know I could'nt scan. Makes sense. I could probably do all I needed from Fox SQL Select without too much trouble.
>
>>Last time I check SQL Server costs, it was $5,000 per processor. So, with 5 users, you're looking at $1000/user and that doesn't include the server.
>I'm aware of that cost. I'm actually looking at MySQL. But I wanted to get all info from people with FoxPro. After all, this is the best place in town.
><bg>
>
>
>>>Hi all,
>>> 1. Should I move to SQL at all (Y/N)? Advantages, Disadvantages.
>>> 2. Basic procedures?
>>>
>>>I have an database written in FoxPro. I'm thinking about moving only the Master table to SQL. The Master table:
>>> 5 million records, grows by 40K+ records a week.
>>> File size is 1 GB to, will grow rapidly due to additional project to be added.
>>> Maximum Foxpro file size is 2GB.
>>> Record size is 187. Will grow to over 230 because of new project.
>>> Currently takes ~8 minutes to do a scan. Across Network, takes 20 minutes.
>>> No more than 5 users, no simultaneous users.
>>> Only manipulation of table is appending new data and reading to create subsets.
>>>
>>> I'm thinking about the SQL solution as opposed to Normalizing the table and making it multiple related table. I would then have to rewrite a lot of code.
>>>
>>> Since I have never worked with SQL, I'm not sure what my results would be. Can anyone help?
>>>
>>>TIA
>>>Pete