
Data in the FSM company database can be retrieved using CoreSQL, an SQL-like language. CoreSQL can be used in the Admin console under Admin → Company → Query API. Besides being the name of the corresponding screen in the admin console, Query API is also the name of the Application Programming Interface in which CoreSQL can be used to read FSM company data.
Query API is a valuable tool for analyzing detail and is widely used in the creation and testing of report templates, business rules, and custom integrations.
Query API / CoreSQL will be discussed in further detail in the Unit "Analytics and Reporting".

FSM company databases have recommended maximum data volumes and record amounts. If exceeded, users may face performance issues when using FSM applications. The recommendations include the following:
- Number of companies for a single FSM Account =< 50
- Database size per Company =< 50 GB
- Attachments database size per Company =< 50 GB
- Maximum recommended table size within a Company DB differs per object, varying from several thousands of records to several millions records per object type.
For mobile applications, different recommendations/limitations apply. Refer to the Unit "Mobile Field Service" for more details.

In order to help limit data volumes in your FSM databases, FSM offers data retention and data obsoletion management.
The data retention management function lets you configure retention policies for supported object types in your company. Removing unused data after a certain time will help ensure that data volumes are kept in line and that a well performing system is attained. Under Admin → Company → Data Retention you can create retention policies for several object types and decide under which circumstances an object instance should be automatically soft or hard deleted from the system. Related objects will be automatically deleted on deletion of the leading object.
Since FSM company data is usually managed by the integration layer to a leading back-end system, it is advised to consider the implications for integration, and to align the solution correspondingly.
Data obsoletion is a way to flag data that is no longer relevant for your field service technicians. This means that the object will remain in your organization's cloud account, but it will no longer be sent to devices during full data synchronization. The data will still be visible in the web applications and other data end points. To set up data obsoletion, maintain the company setting SAP.FSM.Mobile.Sync.DaysSinceLastChangeToMarkObsolete. According to this setting, completed and canceled Service Calls and Activities and their dependent objects are automatically flagged after the defined number of days.

FSM includes several features to monitor the overall solution. On the Account level in the Administration module, Administrators can review:
- Audit logs: containing any Create, Update or Delete Event on account or company level, including details. This feature can be found under Admin → Account → Audit logs
- Authentication and Authorization events: application log-ins and failed permission checks. Navigate to:
- Admin → Account → Authentication events
- Admin → Account → Authorization events
- Events: changes to company and account settings and configurations, as well as executed queries and connector errors. This feature can be found under Admin → Account → Events.
- Business Rule execution logs: statistics and details about executed business rules across all companies in the account. Several overviews exist on the account level and can be accessed as follows:
- Admin → Account → Business Rule Execution Details
- Admin → Account → Business Rule Execution History
- Admin → Account → Business Rule Jobs