SharePoint is not a relational database so it is unfit to host a complex relational data model. This premise is often used by ‘lazy’ developers since it allows them to escape from SharePoint to more familiar ASP.NET/SQL environment. Sometimes even most basic data models are hosted on parallel systems and SharePoint is used only as the front end.
The session will be based on developer analysis of a business case. What are the development options when integrating relational data model into SharePoint? Is SharePoint performance more affected by the model complexity or by data size? When to abandon SharePoint concept?
The core of this session is theoretical, but you will be presented by practical examples of most of the suggested scenarios.