Big project

[mattquantic]

Hi. I am about to start a project that might end up having > a million records.

Is MSSQL better than MySQL for this.

Other than having very efficient queries, stored proceddures and cached queries, is there any architectural methods that I should be emplying?

Such as, having multiple contact tables and a index to tell the sys which one to use - or which ones to join?

M@)

 

[KarveR]

I'd use mysql, I don't have any problems with tables with > 8 million records, don't have the headaches of server reboots like M$, no licensing, no CLA's etc etc.

______________________________________________________________________
There's no present like the time, they say. - Henry's Cat.

 

[mattquantic]

Thanks. Cool

 

[lgarner]

MySQL would be fine. Most of our production stuff is on MS-SQL, but the MySQL server serves about 735 databases, with the largest table around 24M records.

Normal data design would be fine. Nothing special required.

 

[mattquantic]

Really appricate the info. Ta.

 

[snowboardr]

I've seen specs MySQL is faster than MSSQL by a long shot