Sergiy (11/24/2015)

---

Welsh Corgi (11/24/2015)

---

I have three tables that are very large and have too many indexes.

I can easily archive the tables without running into the risk of having to tune the Stored Procedures and embedded T-SQL in .NET Applications.

I do not feel that Partitioning is needed when all that is required is to reduce the size of the tables to improve performance.

The tables will be archived by year so there is not a lot of effort to just archive the tables.

Any thoughts or recommendations would be greatly appreciated?

Size of a table is not a problem.

You do not need to reduce the size of a table to improve query performance.

Archiving, as well as any other type of partitioning are not needed if the indexing for the table is defined correctly.

I offered Scott to show how to achieve better performance using partitioning, but he's pretending he did not see that. He must be too ashamed to admit his ignorance. And too rude to apologise.