We are using SharePoint 2013 On premises version. We have a requirement where I need to store data in SharePoint.
On the home page, users need to take actions on the data and the data that is displayed should not have any latency. Initially, I was planning to use different lists to store the data. But, if I use that approach, I need to pull the data using search as I can’t iterate through 25 different lists to display data on the home page. The problem here is that the data won’t be latest. If a user takes any action on the data, the next user would not see the updated data unless it is crawled and indexed by SharePoint search.
My questions are:
What is the implication if I store all the data in a single list categorized into different content types? I would have 200 items per day. I looked at the column limit and I guess that shouldn’t be an issue as I would have around 100 columns spread into different content types. I would be able to reuse many columns in different content types.
Obviously, list threshold limit is a major concern when there are more than 5000 items in the list. I guess we would hit that limit in a month. But, we are also planning to archive the data 6 months after it is created. So, at a certain point of time, I may not have more than 50000 items in the list. Is this still a very big number?
I also need to use this data to generate different reports. However, I can use search OR SSRS there as that data doesn’t have to be latest.
Any advice on best practices are welcome. Thank you in advance.