Management Reporter - Kill State error

Hi Everyone,

I'd like to share some information about an error we've been seeing recently in MR.  It usually starts with users missing data on their MR reports.  If they rebuild the data mart, everything is correct.  But then next month, or next week, the same thing happens.  If we check the Data Mart Integration logs in the MR Configuration console, we see this error on the Maintenance Task:

You may also see these errors in the MR Service logs:

Insert bulk failed due to a schema change of the target table. 

One or more errors occurred. 

Cannot continue the execution because the session is in the kill state. 

This usually happens because the MR databases on running on the RTM build of SQL 2019 (build 15.0.2000.5 or 15.0.2080.9).  

The version of SQL will be listed in parenthesis after the SQL instance name in SQL Management Studio.  

To correct the 'kill state' error in MR, you'll want to update SQL 2019.

The newest build is CU15.? You can find the full version list here: 

?https://support.microsoft.com/en-us/topic/kb4518398-sql-server-2019-build-versions-782ed548-1cd8-b5c3-a566-8b4f9e20293a#:~:text=SQL%20Server%202019%20Cumulative%20Update%20%28CU%29%20builds%20,April%2006%2C%202021%20%2010%20more%20rows%20 

Some other things that have been known to cause the kill state error are: 

?-A backup or maintenance job running on SQL Server, that interferes with the MR integration tasks. I'd verify this, as we do see it mention that 'DBCC execution completed' right after the kill state/severe error mentioned. 

--Specs on the MR and SQL Server, such as the amount of available memory and CPU.? MR does require a considerable amount of memory.? The recommendation for a small database (50 million GL transaction or less) requires the following: 

32 GB RAM for SQL Server 

16 GB RAM for MR Process Service 

4 GB RAM for MR Application Service 

? 

--If MR is installed on more than one server, such as on a test and live environment and both are pointing to the same SQL databases, it can cause blocking or conflicts. In this case, we would want to stop the MR services on a test environment so only the MR services on the production environment are running. This isn't common, but I wanted to mention it.? A SQL cluster environment would be similar.