July 29, 2013 at 9:12 am
If you really want to stop bulk updates from triggering Lowell's code (please use his code - yours is broken)
...Just put
IF @@ROWCOUNT>1 RETURN
at the start of the trigger...
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
July 29, 2013 at 9:20 am
Ok.. good point on the testing for removed 'review' check (it is a bit column). I was trying to isolate the trigger stamping .. since it is so critical to only capture updates made through the .Net App... I know it is a bit of overkill.
July 30, 2013 at 8:03 am
I set the context_info at the top of the process, then test the value at the top of the Trigger, and bail if appropriate:
Caveat: I have NOT done this through a .NET app, but it should be do-able.
at the top of the process:
SET CONTEXT_INFO 0x42617463685F436F6E736F72746123
And in the trigger:
IF (CONTEXT_INFO() = 0x42617463685F436F6E736F72746123) return;
Mark
Just a cog in the wheel.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply