MySQL Large DB Question

[NSH]

I am undertaking an application to monitor server backup status.
The database wil have, as of now, 900 entries daily with more servers being added regularly.
The database will be used for reporting, etc and I would like it to be as speedy/effecient as possible.

My initial thought was to have one DB for the current month which would hold the current 900+ entries a day data.
Every month a script would be ran to migrate the data for the current month to an archive DB so to keep the current month DB quick.

I am trying to keep the application from being extremely slow and any help on the initial DB design is appreciated!

[nemonoman]

Look: admittedly I am an old experienced hand with this sort of thing. If I were designing a database, id carefully choose data types. I'd normalize. I'd tightnen my queries. I'd index selectively.

I know what I'm doing, so I wouldn't worry at all about the response time until I was approaching 4 or 5 years of records.

On the other hand, if you use poor design, your db will be slow in a few days.