Ontolica Solution Use Case

Integrate databases with SharePoint

Structured data meets unstructured content

Structured data meets unstructured content

SharePoint was made with managing unstructured information, namely documents, in mind. As SharePoint becomes more critical in an organization its role grows beyond document management and the ability to integrate structured data from SQL databases such as MS SQL, Oracle, SAP Sybase and IBM DB2 becomes a requirement.
Master Data Management for SharePoint

Master Data Management for SharePoint

When integrating data from various sources into SharePoint it is often necessary to transform and clean up the data prior to the integration. By putting a Master Data Management (MDM) solution in-front of SharePoint it becomes feasible to normalize and sanitize data to create a “single view” of data that is trustworthy.
Staging of data in-front of SharePoint

Staging of data in-front of SharePoint

SharePoint is not a database even though it’s often used as such. SharePoint is known to encounter scalability and performance problems when handling large datasets. To alleviate this problem it can be helpful to stage a dataset and to keep transformation and aggregation outside SharePoint before integration.
BCS integration is not the answer

BCS integration is not the answer

Business Connectivity Services (BCS) in SharePoint provides basic simple database integration however for more enterprise strength integration BCS does not work. Specifically monitoring, audit trails and alerting becomes critical. Also the ability to stage and transform data in-stream is often a requirement not met by BCS.