I am working on a project to create a new bespoke intranet website for around 50 users. The data volumes are relatively small, but in order to model the data I need to store (about the 100 or so projects my company is currently running) I need to have around 20 different tables in my database schema.
As we were planning on developing this application in MOSS 2007 (our current intranet solution) I am considering using a SharePoint list for each of these "tables" and joining the data together using CAML or LINQ to SharePoint when I need to retrieve it.
In order to give an idea of data volumes, we estimate that we will have no more than 10,000 list items in total across all 20 lists after a year of growth.
My team is split between those who think this is a really good example of embracing SharePoint properly and those who are convinced it will not perform well enough and I will need to use a SQL database instead.
My questions are:
- Is this the right thing to do?
- Do Microsoft offer any guidance on when SharePoint is likely to run out of steam when doing this sort of bespoke development (I can't find any)?
- Does anyone have any experience doing something similar and if so what was performance like?