Thus said "William Attwood" on Tue, 09 Dec 2008 23:16:57 MST:
> Hmmm, if you want, you can do partitioning of that table, so it can
> grow larger and respond faster.
Is the partitioning like Oracle's extents (I think that's what it is
called) where you can dynamically grow a database onto
On Tue, Dec 9, 2008 at 5:50 PM, Kyle Waters <[EMAIL PROTECTED]> wrote:
> I almost sent this to udbug but felt it was more of a general question.
> I have a database with lots of information in it, and find that I need to
> run a report the is going to take up to several minutes to run. It's ok if
Hmmm, if you want, you can do partitioning of that table, so it can grow
larger and respond faster. The functionality is available in MySQl 5.1+.
I would recommend normalizing the data a bit more; a single table for all
clocking in and out, with a FK to a type of clock-in/out, and a FK to the
tabl
William Attwood wrote:
Kyle--
You could upgrade the hardware and/or enhance the storage of the data
through normalization, and RDBMS specific methods such as indexes.
My main problem is that I have to subtract one line from an other, and
then do different things with that data based off a
Kyle--
You could upgrade the hardware and/or enhance the storage of the data
through normalization, and RDBMS specific methods such as indexes.
It is acceptable to store a completed report in another table. If the
report doesn't need live data in the moment, storage of the report is
accepta
I almost sent this to udbug but felt it was more of a general question.
I have a database with lots of information in it, and find that I need
to run a report the is going to take up to several minutes to run. It's
ok if I only run this report once a day in the morning before everyone
comes i
