Dear Mr. Jeremy D. Zawodny,
I am subscriber of the mysql.com MailingList and have received some of you mails.
From the mails I get the idea that you have quite some experience with mysql.
We are planning to migrate our database (currently oracle) to mysql.
Our database consists of about 150 columns (which we are planning to put all into one
table under mysql so that queries run faster and dont have to join different tabels) and
about 300k rows.
The main field type we are using is varchar, tinyint, int, smallint and date. (lots of
varchars).
Queries may run over as much as 15 to 20 columns (some of them varchar, some of them
tinyint).
Queryload my be heavy.
Here are my questions:
1. Is it a good idea to have all the columns in one big table ?
2. Does mysql encounter problems with indexes (speed, performance) when having large
amount of rows ?
3. What kind of server configuration (hardware) would you suggest to get a decent
performance ?
4. How many concurrent threads/queries can we expect to achieve ?
5. Shall we look into replicating (master/slave) to get better performance.
This should be enough for now. Maybe later I will have more questions, but I would be
really thankful if you could give me some help on these issues.
Thank you.
Mit freundlichen Grüßen
Florian Wilken
OMANDU GmbH
Waldenserstr. 35
10551 Berlin
Tel.: 030-39037364
Fax.: 030-39037365
At 12:58 07.05.02 -0700, you wrote:
>jzawodn@stripped
