Oh....
I forgot to mention...MySQL crashed after 48 million rows.
I'm willing to accept that I may not have configured MySQL perfectly for performance, or possibly not even for the stability needed for a dataset of that size.
I guess the point is that, out of the box, SQL Server worked very well and MySQL didn't.
Cheers, :-)
Clinton
Thanks dude. ! I agree with you, cause of costs cut, we decided to move to a free database. So the same data , same indexes, same query are much more slower on MySQL than SQL 2005
I came back and start to tune my.cnf parameters.. got some speed, but still a crap..
Actually I have MySQL .Net provider . I use iBATIS for a Windows application..
I'm not even close to JDBC..but I can see what is it performance, because MySQL QueryBrowser and Admin are using java and JDBC and they are hanging up very ofen L
It could be the driver for sure...but really, how different is the ADO.NET driver from the JDBC driver? I'd imagine they're very similar.
Also, I'd be surprised if Microsoft wrote a driver for a competing technology that's better than one of the most popular database/platform combinations in the world (Java/MySQL).
I really think it's just the database. I tried both MyISAM and InnoDB. SQL Server 2005 Developer Edition just destroyed them both.
Cheers,
ClintonOn 10/19/06, Brian Kierstead <[EMAIL PROTECTED]> wrote:
Is it MySQL or JDBC that is slower? I've never used it JDBC, but I know that ODBC is noticeably slower.
Brian
Clinton Begin wrote:
Other than that MySQL is a heck of a lot slower than MSSQL, no. :-)
I recently loaded the netflix prize data (100,000,000 rows), and using cached prepared statements, batch updates, with transactions from 1000 - 10,000 records at a time.....
MSSQL was 3x faster than MySQL using JDBC (so not ADO.NET), but same difference.
Cheers,
ClintonOn 10/19/06, Dorin Manoli <[EMAIL PROTECTED]> wrote:
iBATIS is slower with MySQL provider that MSSQL .. does anyone accouter such problem?
