Table of Content:
- The Model
- De-normalisation
- Indexes
- Conclusion
Database performance tuning and optimisation
Welcome to an introduction on database performance tuning and optimisation. My previous tutorial, SQL Made Simple, lookedata normalised database, and explored some of the queries we would use to make information from data in its normalised state. Today, we’re going to look at ways to shorten query processing time on this same database.
Optimising databases is a balance between normalised data and optimised queries. We look at two ways to find this balance; de-normalisation, and the use of indexes. We'll de-normalise our design just a little to remove unnecessary table joins. We also make use of a new status code value to eliminate a query entirely. We look at indexes and the performance gains they give us, and consider their use in the context of search functionality.
Optimising databases is a balance between normalised data and optimised queries. We look at two ways to find this balance; de-normalisation, and the use of indexes. We'll de-normalise our design just a little to remove unnecessary table joins. We also make use of a new status code value to eliminate a query entirely. We look at indexes and the performance gains they give us, and consider their use in the context of search functionality.
Robert Stuttaford
I live in Cape Town, South Africa. I've been pushing 1's and 0's ever since my first computer at the age of 11. Ever since then I've always known I'll be a geek. I now work for Wireframe Studio in sunny Cape Town, and have been for the last 3 years. I'm the database / ASP / dynamic Flash guy here. I'm also one of the XHTML / CSS guys. I have alot of fun in my work because I develop solutions in a variety of ways. I always have something to do, and one project is always different to the next. I actually do have a girlfriend amongst all that!