Scom console slowness and sdk is not repsonding due to blocked session

Question

I have some issue with scom console slowness and opsdb sdk. I can guess this one is due to blocked session and the query which is blocking is

CREATE PROCEDURE [dbo].[p_EntityTransactionLogBegin]

(

@DiscoverySourceId uniqueidentifier,

@ContextGenerated nvarchar(255) = NULL,

@TransactionId bigint = NULL OUTPUT

)

AS

BEGIN

SET NOCOUNT ON;

DECLARE @Err int;

DECLARE @LastModified datetime;


UPDATE [dbo].[DiscoverySource]

SET [TimeGeneratedOfLastSnapshot] = [TimeGeneratedOfLastSnapshot]

WHERE [DiscoverySourceId] = '85AB926D-6E0F-4B36-A951-77CCD4399681'

SELECT @Err = @@ERROR;

IF (@Err <> 0) 

   GOTO Error_Exit;



SET @LastModified = GETUTCDATE();

INSERT INTO dbo.[EntityTransactionLog]

(

    [DiscoverySourceId],

    [ContextGenerated],

    [LastModified],

    [TimeAdded],

    [IsCommitted]

)

VALUES

(

    @DiscoverySourceId,

    @ContextGenerated,

    @LastModified,

    @LastModified,

    0

);

SELECT @Err = @@ERROR;

SELECT @TransactionId = @@IDENTITY;

IF (@Err <> 0)

    GOTO Error_Exit;

IF OBJECT_ID('tempdb..#EntityTransaction') IS NOT NULL

BEGIN

    INSERT #EntityTransaction

    (TransactionId)

    VALUES

    (@TransactionId);

END

RETURN 0;

Error_Exit:

RETURN 1;

END

GO

It looks similar an issue as described in this link

https://social.technet.microsoft.com/Forums/en-US/03fce427-06ca-4667-898f-ffbfcd8535ef/really-expensive-discovery-insertion-how-can-i-trace-it-back?forum=operationsmanagergeneral

but does not any promising solution.

Does anyone have gone through this issue?

Answer 1

Same ploblem, i can't find solution yet. It's sad that the community has no idea about this.