I was putting together a demo involving BAM’s real time aggregation capability, and was interested to see that it the aggregation was calculated via a SQL trigger, which stores the aggregated data in a SQL table. This differs to non-real time aggregation, which BAM implements with OLAP / SQL Analysis Services. OLAP / SQL Analysis Services is geared towards aggregating large sums of data. SQL tables (like the ones used in BAM’s real time aggregation implementation) are relatively less capable of this aggregation task. This makes the maintenance of the real time aggregation table important – especially keeping the number of rows in the table to a level allowing reasonable query performance. The BAM Management Utility in BizTalk Server 2006 provides a handy command to do just that: set-rtawindow Note – the BAM Management Utility also provides a command to set the duration of a non-real time aggregation activity: set-activitywindow See the following link for more information: http://msdn2.microsoft.com/en-us/library/aa547898.aspx…
Search this Site:
Recent Posts
- Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
- BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
- BizTalk Oracle Adapter error: The assembly required for type mapping not found.
- PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
- Friday (funny) Fact: There is no size limit for the Logic App parameter name