SQL deadlock Exception in ProcessUsers on user (SQL ID: (4374771)

SQL deadlock Exception in ProcessUsers on user (SQL ID:

While running profiles logs in sync show the following detail in log files shows when performing a profile run over user objects on table bt_person:   

Error  Exception in ProcessUsers on user  (SQL ID: 65705)
Transaction (Process ID 70) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
   at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
   at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
   at System.Data.Linq.ChangeDirector.StandardChangeDirector.DynamicUpdate(TrackedObject item)
   at System.Data.Linq.ChangeProcessor.SubmitChanges(ConflictMode failureMode)
   at System.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode)
   at BinaryTree.DirSync.Exchange.ADEndpoint.ProcessUser(BT_Person person, BTCodexDataClassesDataContext DB)
   at BinaryTree.DirSync.Exchange.ADEndpoint.<>c__DisplayClass351_0.<ProcessUsers>b__7(Object item)

 

In this case, the result of the deadlock was a lack of resources in the SQL Server, not allowing it to perform updates fast enough.  

Increase the amount of resources for the running of the SQL DB associated with the product.  Ensure enough RAM and CPU is assigned to the server,  Depending on your platform, you will need to restart the server to apply the changes.  In Some cases, when the machines are virtualized, ensure that proper assignment of CPU has been achieved. 

Note: running SQL Express hinders the processing power of the SQL server due to Microsoft limitations on the product. SQL Express should be used when performing POC, testing, Lab environments, avoid as much as possible using SQL Express unless the solution architect has identified the scope of the project does not require SQL standard or Enterprise. Due to Limitations on SQL Express a Migration project moving from Proof of Concept to Production can be problematic due to limitations on performance, DB size limitations etc.