Notes for PB + MSSQL + triggers

Petabyte + MSSQL + trigger must note: If the trigger has more than two returned values, such as two update statements, the trigger is misjudged to have changed the data and the disk is not saved successfully. Tip: Rowchangedbetweenretrieveandupdate. Nochangesmadetodatabase. Therefore, the MSSQL trigger must be processed as follows: the trigger starts to add: if

PB + ms SQL + trigger must note: If the trigger has more than two returned values, for example, two update statements, the trigger is misjudged as data has changed and the disk is not saved successfully. Tip: Row changed between retrieve and update. No changes made to database. Therefore, the ms SQL trigger must be processed as follows: the trigger starts to add: if

Note the following before using PB + ms SQL + triggers:

If the trigger has more than two returned values, for example, two update statements, it is misjudged that the data has changed and the disk is not saved successfully.

Tip:

Row changed between retrieve and update.

No changes made to database.

Therefore, ms SQL triggers must be processed as follows:

Trigger start adding:

If @ ROWCOUNT = 0 Return -- improves performance

Setnocount on -- no statistics are returned, which can reduce frequent network response and improve performance efficiency; Avoid misjudgment as data changes (sybase does not have such problems)

...

...

Termination plus:

Setnocount off