Pages

08 September, 2024

SQL Server options to handle a large table, from the options listed below [closed]

I have a SQL Server database with a table that contains 50 million rows, I expect the row count to growth to 700 million rows by the end of my processing cycle. The current table performs well, and it’s been tuned with the appropriate indexes.


In order to scale the database, and for performance, I am considering the implementation partitioned tables, however, I keep reading about downsides. I wanted about your experiences and preferred approach between the options listed below, in the context of implementation ease, efficiency and subsequent maintenance:



* Partitioning table

* Indexed views

* Sharding

* Filtered indexes

* Partitioned views

* In-Memory OLTP

No comments:

Post a Comment

Thanks