Compilation taking long time after schema extension

Check the dialog journal to see why those two dbqueue tasks are going into reset.

Hi Troy,

I see belwo entries is dialog journal.

#LDS#Processing is disabled (deactivated trigger(s)).|
#LDS#Temporary lock for task {0}, {1} retries left.|QBM-K-QBMConstraintDisable2| 2|
#LDS#Temporary lock for task {0}, {1} retries left.|QBM-K-QBMConstraintDisable2| 2|
#LDS#Temporary lock for task {0}, {1} retries left.|QBM-K-QBMConstraintDisable2| 3|

Can I cancel window and compile database.

Hi,

If you have deactivated triggers, try this:

Find disabled triggers:

SELECT DISTINCT o.NAME
,CASE o.type
WHEN 'U'
THEN 'Table'
ELSE ''
END AS TableType
,CASE '%'
WHEN '%'
THEN 'all'
ELSE '"' + t.NAME + '"'
END AS Triggername, t.is_disabled
FROM sys.objects o
JOIN sys.triggers t ON o.object_id = t.parent_id
WHERE o.type IN ('U')
AND o.NAME LIKE '%'
AND t.is_disabled = 1
AND (
0 = 0
AND t.NAME LIKE '%'
OR 0 = 1
AND t.NAME NOT LIKE '%'
)
ORDER BY 1

Enable all triggers:

Exec QBM_PtriggerEnable '%', '%'

Hopefully that will fix your issue.

B.

even after enabling triggeres its getting disabled automatically ,

Also it is showing as one identity manager database is in mentainance mode.

This is what happens when changes are made, all of the constraints are disabled and then reenabled with the changes. If the dialog journal is not giving anything useful you could always check the qbmdbqueuecurrent table in SQL Management Studio to see what the UID_Parameter and UID_SubParameter are showing. It should give an hint to what is the issue.

This is what happens when changes are made, all of the constraints are disabled and then reenabled with the changes. If the dialog journal is not giving anything useful you could always check the qbmdbqueuecurrent table in SQL Management Studio to see what the UID_Parameter and UID_SubParameter are showing. It should give an hint to what is the issue.

I did checked qbmdbqueuecurrent and both UID_Parameter and UID_SubParameter has NULL value.

I noticed that in qbmdbqueuecurren slotnumber get updated to -2 and again to 0

slotnumber -2 means that the task was locked by another process. This makes sense based on the warnings in the dialog journal. Check Activity Monitor in SQL Management Studio, then click on Processes and see which Session ID has it locked.

thak you Troy, finaly I am able to compile database.