Best database to use

[zplayer]

ok here goes;

Database would be populated with in excess of 100,000,000 records every day. Possibly single inserts or partial bulk loads .

Each day fresh database would be used.

Data would be stored in 6 largish tables (approx 30-40 columns each)

Users could query the data (and in some cases would run time consuming query's accross all tables) but wouldn't be able to alter data.

Speed of the query's is a high priority.

Tables would need backed up (low priority)

Hardware's not an issue

I'm thinking mysql but have concerns over table locking effecting querys while constant inserts or bulk inserts happening - or would this not be an issue??

[MAK]

You could choose any RDBMS for this. I would recommend you to choose SQL Server 2005 or Oracle 10G or DB2 for many of their features and native support for large tables and partition.

You could also evaluate TeraData.

[rmiao]

What's frontend? May choose rdbms that easies your frontend work.

[zplayer]

Front end will be a php web interface, and also a gui app written in QT.

Sorry for the delay, I've been away