I think a good DBA can solve most of your problems with the current database. MySQL is know for quite good performance.
First thing I can think of ... In SQL Server you can join like this inner join myTable t with (nolock) on ..... Improves performance a lot when you don't look tables. Investigate if MySQL have something simular. /Andreas On Fri, Dec 10, 2010 at 11:29 AM, Thomas Mueller <[email protected]> wrote: > Hi, > > If you have highly concurrent read and write load, then PostgreSQL > might be better (than both MySQL and H2). H2 does support MVCC, but > not combined with multi-threaded kernel currently (so long running > statements are a problem if you use MVCC). If you need very higher > performance, and if an embedded Java database works for you, H2 is > probably better, but it's hard to say in your case. > > I guess the best solution would be to code your application more or > less independent of the database, and then try a few. But that might > not be easy in the short term, unless you use tools such as Hibernate > or EclipseLink. The advantage in the long term is that you are not > stuck with one database. Supporting multiple databases might be good > for development (for example using H2 for most of the testing, but > PostgreSQL for production). > > Regards, > Thomas > > -- > You received this message because you are subscribed to the Google Groups "H2 > Database" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=en. > > -- Andreas Henningsson "Vanligt sunt förnuft är inte särkilt vanligt." -- Voltaire -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
