The limitations (unexpected) of SharePoint 2010 and/or the way that the "views" work in the ArcGIS for SharePoint create severe performance limitations. SharePoint Views are currently used to filter data. These were created for 2 reasons: To limit the number of records that are retrieved; and to limit the attributes retrieved to a minimum. It appears that the View concept in SharePoint (or ArcGIS for SharePoint) ignores these limitations, causing ALL data to be retrieved. The following re-factor should be considered:
Reduce the main table to only the bare minimum of columns and consider "lifting" some values out of the raw XML where needed (e.g. Earthquakes have structured parameter data in the XML that is useful for filtering).

Last edited Jun 24, 2013 at 11:53 AM by cloop, version 1


No comments yet.