I am new to SharePoint and I need help on the best way to architect our database.
Our Division has multiple groups and each group has multiple projects.
Each group is a site, so we have multiple group sites. And each project is a sub site under the group site and there a Task for every project.
G1 -> P1, P2, P3 …..
G2 -> P1, P2, P3 …..
Currently we have separated Task (Action Items) database for each projects. Do you think it wise to have these many databases to manage or should we have only one master database for each group and add column for projects? But what about in the long run when we have thousands of Action Items? Would it bogged down the SharePoint when the user select display “all” action items? We have different scenarios below.
Scenario #1: Joe is working on three projects and would like to pull all of his action items into one view. “Joe’s Action Items List” to show all the Action Items (tasks) he wrote and that are assigned to him. Joe can also filter by Projects or Status in his view.
Scenario #2: Joe’s Manager (who does not write Action Items nor has anything assigned) would like to see the all Overdue/Late items across all Projects.
Scenario #3: Users can search for Action Items across multiple databases – including their own action items. User uses Action Item tracker personally to track his to do’s. So he could run a Report by selecting All databases or selective databases for his query.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!