I am having an app reading and writing to a Sharepoint list. The list is getting larger and larger (now 2000 records, antipating over 50,000 or more) in the same pace of the rollout. Before it's too late, I'm considering whether or not to apply an index to the Sharepoint list to improve the reading performance as my app is to read more frequently than write to the list.
I have a filter query in the app filering these fields:
- DateInText (a text field containing a date to solve the delegation issue)
Do you have any advice on whether applying index? If so, which column should the index be applied on?
Thanks @RezaDorrani . I read some articles saying that adding index may not be beneficial sometimes, like more storage required, slow writing speed. So if I to add an index, I think I should add the most efficient one.
Do you have any idea or advice whether I shall create a simple index of a column or a compound index ?
Having indexes on your SP list would earn more benefits than making INSERT/UPDATE/DELETE transactions slow.
Please review if you really need 2000 records for non-delegable operations. Reducing Data Row Limits to 500 from 2000 would improve performance obviously, benchmark proved min 20% of performance gain at P99 percentile.
If your SharePoint list has many columns which might not be neccessary all of them, you can also create a view in sharepoint and use Flow to retrieve sharepoint view data. This would reduce the amout of retrieving data out of SharePoint list.
For long-term, considering other data sources like CDS would be recommended.
Please feel free to share a SessionId or AppId of your app with mentioning me. Then, I would check telemetry.