TAG | Why 90% of production databases aren't indexed properly |
|
| by David M Williams | |
| Wednesday, 18 February 2009 | |
|
Page 1 of 3   
Featured Whitepaper
5 Best Practices for Smartphone Support
What I’m talking about here comes down to one simple thing: indexing. That’s it. Ok, sure, most developers and designers know they ought to index important fields. The database system will itself index the primary key by default. (The primary key is the record or combination of records that uniquely identify any single row. For instance, a car registration plate is a natural primary key, as is a social security number or tax file number. A person’s first name is not a primary key because it has no guarantees of being unique in any arbitrary table of people.) Actually, it’s possible to over-index a database. Every index will add time when data is inserted, deleted or modified because the database system has to adjust all those indexes. However, I’m talking about something different. Clustered indexes. And I’m sick and tired of seeing clustered indexes ignored. Let me tell you just what a clustered index is and why it matters. I’ll even show you with a real-world leading financial application. |
| < Next story in category | Previous story in the category > |
|---|
