This article contains steps on how to remove the capacity consumption of the “-analytics” tables, which involve disabling solution settings and uninstalling solution components. Before proceeding, please make sure that the analytics and insights features are not being used in the environment.
Tables ending in “-Analytics” hold data related with predictive insights and/or analytics dashboards, which are synched from Microsoft Dataverse entities into Azure Data Lake Storage, for each of the following applications:
- Sales Insights
- Customer Service Hub
- Field Service
- Resource Scheduling Optimization
If one or more of the above solutions is installed in an environment, is possible that one or more tables will be generated to hold the information being produced by the respective functionality. Some examples of the functionalities that utilize the Analytics tables are Relationship Analytics, Predictive lead/opportunity scoring, Sales Insights cards, conversational intelligence.
Table to solution mapping
These are some of the most common tables that are generated for Analytics for each solution. Do note that this is not an exhaustive list and further entities may be added or removed.
Customer Service Hub (msdyn_AnalyticsForCS) |
Sales Insights (SalesInsightsMDLConfig) |
Field Service (msdyn_DataInsightsAndAnalyticsForFS) |
Resource Scheduling Optimization (msdyn_DataInsightsAndAnalyticsForRSO) |
incident | queue | resource | bookableresourcebooking |
incidentresolution | systemuser | msdyn_priority | msdyn_resourcerequirement |
subject | organization | msdyn_routingoptimizationrequest | territory |
queue | account | msdyn_routingprofileconfiguration | calendarrule |
queueitem | contact | calendar | bookableresourcegroup |
activitypointer | lead | msdyn_optimizationrequestsource | bookingstatus |
systemuser | opportunity | bookableresource | msdyn_bookingtimestamp |
appmodule | team | bookableresourcegroup | organization |
organization | phonecall | msdyn_resourcerequirement | |
territory | |||
appointment | calendarrule | ||
activityparty | organization | ||
connection | |||
businessunit | |||
metric | |||
opportunityproduct | |||
product | |||
opportunitysalesprocess | |||
processstage | |||
connectionrole | |||
workflow | |||
gole | |||
role | |||
systemuserroles | |||
msdyn_autocapturesettings | |||
msdyn_autocapturerule | |||
leadtoopportunitysalesprocesses |
Step 1 | Confirm which analytics features are enabled
It is possible to confirm which analytics features are enabled for an environment by either checking each individual application and confirm if the analytics and insights is enabled (same steps are the ones mentioned to remove their consumption in the next section), or use the connection to SQL Server Management Studio to retrieve this information.
Please review the public documentation on how to connect to your environment database here and make sure that the TDS endpoint is enabled in Environment Settings in the Power Platform Admin Center.
After connecting to the database, you can execute the following query to retrieve a list of the analytics features available for your specific environment and what is their current status:
SELECT msdyn_datainsightsandanalyticsfeature.createdon,
msdyn_datainsightsandanalyticsfeature.solutionid, solution.friendlyname,
solution.description, msdyn_name, msdyn_provisionstatusname, msdyn_isenabledname
FROM msdyn_datainsightsandanalyticsfeature
JOIN solution
ON msdyn_datainsightsandanalyticsfeature.solutionid = solution.solutionid
Example result:
Through this query you can review what is the name of the solution (friendlyname) that includes the analytics features (msdyn_name); if the feature has been provisioned in the environment (msdyn_provisioningstatusname), and what is its current status in the environment (msdyn_isenabledname).
Step 2 | Disable analytics features
Please make sure that the analytics and insights features are not being used before executing any of the following steps. If you wish, at any point, to revert the analytics functionalities for a given environment, you will need to re-enable the historical analytics setting for the respective application. only the setting that was disabled needs to be enabled again.
In order to reduce the capacity consumption of the analytics tables, the respective solution that is connecting to Managed Data Lake needs to be uninstalled from the environment or the analytics capability of the solution needs to be disabled. If there’s an entity that is shared between multiple solutions, you may need to remove both of them in order to cleanup the respective analytics table, otherwise the consumption will remain.
> For Sales Insights
To remove the consumption of Analytics tables created by Sales Insights, the SalesInsights MDL solution needs to be uninstalled from the environment:
At the moment, if any solution or system update is deployed to Sales Insights, the MDL solution will be generated again and the tables may once again be created. The workaround for the time being is to uninstall the MDL solution again, until this behavior is patched, or uninstall SalesInsightsAddOn as well.
> For Customer Service Hub
The analytics and insights capabilities for Customer Service Hub are enabled manually for each environment.
Customers have the option to opt-out of this feature, which will remove all the -Analytics tables dependent on Customer Service Analytics, by following the below steps:
- Access Customer Service Hub > Service Management
- Scroll on the left side panel to Analytics and Insights and click Settings
- Access Customer Service historical analytics (preview)
- Disable the feature
Make sure that the solution Insights and Analytics for Customer Service historical analysis (msdyn_InsightsAnalyticsCSHistoricalAnalytics) is uninstalled after this setting is disabled.
> For Field Service
The same steps for Customer Service Hub apply to Field Service; as such, in order to disable the consumption of analytics and insights for Field Service, the following steps can be followed:
- Access Field Service > Settings
- Scroll on the left side panel to Analytics and Insights and click Settings
- Access Field Service historical analytics
- Disable the feature
Make sure that the solution Insights and Analytics for Field Service historical analysis (msdyn_InsightsAnalyticsFSHistoricalAnalytics) is uninstalled after this setting is disabled.
> For Resource Scheduling Optimization
The analytics tables created after the installation of RSO are associated with reporting capabilities for this solution. The previous steps apply to this solution as well:
- Access Resource Scheduling Optimization application
- Scroll on the left side panel to Settings > Analytics and Insights
- Access Resource Scheduling historical analytics
- Disable the feature
Step 3 | Monitor the capacity report
Once any of the action plans above are applied to the environment, the “-analytics” tables associated with a particular solution, should be automatically removed between 24h and 48h. If, following this time range, the tables are still present in the capacity report or if you see an entity generated in File Capacity which you are unsure to which solution it belongs to, please raise a support request with Dynamics 365 technical support team.
See also