This section shows the available API objects and provides more information on executing SQL to SAP ByDesign APIs.
- The connector models SAP ByDesign Analytics Services as relational views. Entities defined on a Custom Service are modeled using a combination of tables and views, allowing you to write SQL to query SAP ByDesign data.
- Live connectivity to these objects means any changes to your SAP ByDesign account are immediately reflected when using the connector.
Views describes the available tables. Tables are dynamically defined entities available on the CustomService.
Views describes the available views. Views are dynamically defined either from the Navigation Properties off a CustomService, or from the queries on an AnalyticsService.
Collaborative Query Processing
The connector offloads as much of the SELECT statement processing as possible to SAP ByDesign and then processes the rest of the query in memory. API limitations and requirements are also documented in this section.
See SupportEnhancedSQL for more information on how the connector circumvents API limitations with in-memory client-side processing.
To retrieve reports of an analytics service, you must specify the AnalyticsService property. All the reports are exposed as views. Note that client-side filtering will be disables if one tries to perform an unsupported by the SAP ByDesign API filter on a dimension and at the same time does not include that dimension in the SELECT clause.
If you want to make use of client-side filtering (executing filters that are not supported by the SAP ByDesign API), you need to include the dimension in the SELECT clause.
Also, if the query is a star query and the number of the dimensions is higher than 15, the driver will use only the default dimension and ignore the others. This is done because it is really hard to give sense to a result set with too many dimensions. This use case is common when the driver is used in various tools. The default dimension is chosen dynamically randomly by the driver.