In a previous tutorial titled “ASP.NET Web Development and Hosting” (published October 25th), you learned how to develop ASP.NET websites using Mono Project and deploy them in your existing Linux-Apache hosting account. The example ASP.NET mono website, http://www.dotnetdevelopment.net/, did not use

(Rob Gravelle) A poorly optimized query can become the bottleneck in an otherwise highly optimized process. In many cases, the source of the slow performance is improper table joining in the WHERE clause. With that in mind, this article looks at ways to optimize table joins for speedy data retrieval

(Peter Zaitsev) Understanding how well your tables and indexes fit to buffer pool are often very helpful to understand why some queries are IO bound and others not – it may be because the tables and indexes they are accessing are not in cache, for example being washed away by other queries.

(Chris Schneider) Point in time backup and recovery is a crucial component of any part of any MySQL environment. This article describes how to implement the basic point in time recovery and describes a few mechanisms to accomplish this goal.

(Peter Zaitsev) Innodb/XtraDB tables do benefit from being reorganized often. You can get data physically laid out in primary key order as well as get better feel for primary key and index pages and so using less space, it is just OPTIMIZE TABLE might not be best way to do it.

(Leo Hsu and Regina Obe) In Intro to PL/R and R, we covered how to enable PL/R language in the database and wrote some PL/R functions that rendered plain text reports using the R environment. What makes combining R and PostgreSQL in PL/R most powerful is when you can start writing SQL summary querie

(Peter Zaitsev) One data point which is very helpful but surprisingly few people have is the history of the table sizes. Projection of data growth is very important component for capacity planning and simply watching the growth of space used on partition is not very helpful.

(Shlomi Noach) So you have a running MySQL server, it’s working well and everyone’s happy. You want to make a minor change to the configuration file, so you edit the file, restart MySQL – but the change doesn’t catch!

(Mark Callaghan) How do InnoDB and Postgres store large columns? Both use overflow pages for rows with large columns and support compression. Postgres is more likely to store large columns in overflow pages and InnoDB is likely to use more space in overflow pages.

(Kedar) Do you ever need to transfer databases between servers? Different OSes?