Overall Satisfaction with MS SharePoint / SQL
SharePoint is used as a document management system, for portals, team sites for collaboration, across whole organization. SharePoint solves one main problem - preserving and managing organizational knowledge.
- Simple to implement in vanilla approach
- Big community
- The main pros: it's big platform which can be customized in very simple way to relevant business need. And this is a big con too
- Good UX
- Based on implementation - not so big maintenance cost.
- Can be fully implemented as self-service approach - users can create sites/libraries/pages by themselves.
- Performance, when implementing in global environment
- Limited actions in OOTB Workflows
- No OOTB option to create Read-only columns in Lists
- No OOTB option to create dependencies between columns in the List
- Too many helper tools, need to know where to use and how to start
- Lock-in with Microsoft
Using MS SharePoint / SQL
3000 - Everything
5 - 2 implementers
2 developers
1 system adminitsrator
2 developers
1 system adminitsrator
- DMS
- Portals
- Forms
- Using SharePoint on the cloud giving option to share content with users outside organization without adding licenses
MS SharePoint / SQL Implementation
- Vendor implemented
- Implemented in-house
Change management was minimal
- To make sure that vendor solution supported by Microsoft
- Invite Microsoft to review design and approve it
- Microsoft gold partner not mean that you will have supported solution