Blockings - create trigger on big tables

rixrix

Hello friends

We have NAV 4 , SP3 and a TOO MUCH of blockings are caused by such commands as below.
They happen on several BIG tables like „Item Ledger Entry“, „Value Entry“, ...

And Nobody here (implementing company, Microsoft, ...) knows WHY ?

Can you help us to identify the cause?

CREATE TRIGGER "dbo"."VEREX-ELTO$Item Ledger Entry_TG" ON "dbo"."VEREX-ELTO$Item Ledger Entry" FOR DELETE, INSERT, UPDATE AS
SET NOCOUNT ON
DECLARE @del_count int
DECLARE @ins_count int
SELECT @del_count = count(*) FROM deleted
SELECT @ins_count =


Thank you

DenSter

If your implementing company doesn't know what they do, then you need to find another implementing company *right now*. Those are the SIFT triggers.

rixrix

Thank you ....

After some while they said , it is something with SIFT :-)

But they do not know why there are so much of them and whay they are causing "BIG" blockings .....

Are that queries generated by NAV as system queries or do they depends on implementation code?


Thank you

kriki

Those triggers are created by NAV to update the SIFT-fields. It is the system used until NAV4.0SP3 and 5.0.
Starting with 5.0SP1 the system has been changed and is more efficient but you need SQL2005 or higher.

And like Denster wrote : search another implementing company. One that know how to tackle those problems.

DenSter

Whatever you do.... DO NOT TOUCH those triggers, LEAVE THEM ALONE. If your partner doesn't know what they are, they are simply unqualified to be your partner, I don't care how many certifications they have.

Marije_Brummel

Well, you must admit, the parner has managed to find out that the triggers caused the blocks. That's something to start with and shows to me that they have some SQL Skills.

Sri Lanka is not Europe or the USA. Give them a break. Search a freelance specialist to tackle this problem and live many happy days using Navision.