Articles tagged with: non-clustered index
Optimal performance in SQL Server OLTP (Online Transaction Processing) systems is achieved by creating balance between insert, update, delete, and select. Which is most important — adding data to the database, or retrieving it back in a report or application? The answer is yes! The very reason we save data is so that we can retrieve it. We also need to modify the data and delete non-relevant data.
In a previous blog post, I discussed the value of indexing. The real value is to help us retrieve data quickly. No one likes to wait for data from the database. We want instant answers and indexes are the best way to facilitate that.
Well then, why not create a lot of them? Why not create an index to match the way we search or sort in each query? The answer is the negative impact on the server when we modify data.
Here’s the secret — the most important thing to know about SQL Server (in my opinion) is indexing. In transaction processing systems (also known as OLTP databases), database activity involves several statements. These include insert, update, delete, and select. There is a competing need between the modification statements (insert, update, and delete) and reading the data (select). Since the database has both — what should we do?