[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql-internals
Subject:    Re: database design
From:       Russell E Glaue <rglaue () cait ! org>
Date:       2001-11-14 17:26:59
[Download RAW message or body]


This is the wrong list for this question.

In any case, you will find things will speed up when you correctly apply
indexes to your database tables.
-RG


On Wed, 14 Nov 2001, Shuyan Qiu wrote:

> Date: Wed, 14 Nov 2001 09:15:11 -0700
> From: Shuyan Qiu <shuyan@s4rec.com>
> To: internals@lists.mysql.com
> Subject: database design
>
> Hi,
>
> I'm a mysql database user. In our relational database we have 30-50 tables,
> some tables contain 7000-3000 records, some tables have 300-500 records. When
> we use php to run mysql database reports, it's very slow. So, if we create
> one big table for our database, put all fields together in this one big
> table, there is no relationship, this way we can avoid the complicated
> queries when we run reports. Will it run the reports faster?
>
> How can we speed up?
>
> Please help!
>
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
>
> To request this thread, e-mail internals-thread2275@lists.mysql.com
> To unsubscribe, e-mail <internals-unsubscribe@lists.mysql.com>
>
>


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail internals-thread2276@lists.mysql.com
To unsubscribe, e-mail <internals-unsubscribe@lists.mysql.com>

[prev in list] [next in list] [prev in thread] [next in thread]