This constant need for added space can quickly balloon into a serious storage issue for enterprises that index a lot of data. All the data that is not part of a clustered data index now needs its own storage space. SQL Server scalability figures show that each cluster uses 50 instances of SMB storage or 25 instances of SAN storage.Īdditionally, when data is indexed, the indexing process can take up additional storage space. Across thousands of rows of data, these processes can consume too much storage and impact overall performance. Functions are constantly running to keep the numbers up to the minute, while indexing analyzes this data in order to sort it. The constant need to keep the data accurate and indexed causes competition within the data table. However, the negative impact of indexing this data can be seen in multiple ways. With multiple indexes to categorize and organize the information on hand, analyzing and retrieving the data should theoretically be much easier. Indexing this data may seem like an obvious solution. Getting the best possible performance from a SQL server can become more complicated as you add more operations to your database.įor example, online transaction processing requires the ability to add and delete data, modify selected data, and retrieve it quickly.

Sql server indexing