Consider the following scenario:
In this scenario, the background process during the staging process may encounter an infinite loop when the background process internally calls the [mdm].[udpMemberRecursiveCircularCheck]
This issue occurs because the udpStagingSweep
procedures call the udpMemberRecursiveCircularCheck procedure one time for each staging row. This behavior should check a domain-based attribute value, and returns an error if the staging row causes a circular reference together with the existing data. After all staging rows are checked, you receive the following results:
- The staging rows without errors are applied.
- The staging rows with errors are noted with an error code.
If the conditions that are described in the "Symptoms" section are true, the [mdm].[udpMemberRecursiveCircularCheck]
procedure loops indefinitely until either the server resources are exhausted, or a time-out occurs.
Cumulative update information
SQL Server 2008 R2 Service Pack 1
The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1
Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this issue, use one of the following methods:
- To prevent the issue, follow these steps:
- Manually review the member data values that are being inserted into the staging table before you run the staging process.
- Make sure all member values for any domain-based attributes do not contain circular references that are described in the "Symptoms" section
- When the issue that is described in the "Symptoms" section occurs, follow these steps to correct the issue:
- Identify the session that is running in the infinite loop.
- Kill the session to stop the loop.
- Delete the circular reference values from the staging table before the circular reference is processed again.
- To identify which session to kill, use one of the following methods:
- Use an activity monitor in Microsoft SQL Server Management Studio.
- Select from the sys.sysprocesses or sys.dm_exec_requests dynamic management view (DMV) to identify the sessions that are working inside the MDS database in which the CPU and time are incrementing quickly. Make sure that the current query that is running on the session matches the procedure names that are described in the "Cause" section.
- To identify the currently-running procedure for the sessions, use one of the following methods:
- Right-click Details menu on each process in the activity monitor processes listing.
- Use one of the following parameters:
- The DBCC INPUTBUFFER (spid) command together with the session ID.
- The SELECT * FROM sys.dm_exec_sql_text(sqlhandle) function together with the matching SQL handle parameter when you use the DMV output.
For more information about how to open an activity monitor in SQL Server Management Studio, visit the following MSDN website:
For more information about the KILL
syntax, visit the following MSDN website:
For more information about the sys.dm_exec_requests
DMV, visit the following MSDN website:
For more information about the sys.dm_exec_sql_text
DMV, visit the following MSDN website:
For more information about the DBCC INPUTBUFFER
command, visit the following MSDN website:
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates