Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Procedural code automatically executed in response to a database event.
2
votes
Accepted
Trigger/Event that fires when a Transaction finishes
For instance, in the scenario:
one or two ADO.Net applications
one or two EntityFramework applications
one or two SSIS jobs
each potentially modifying the data on those tables, I would:
create a trigger … Even if it were possible to intercept a COMMIT by a trigger, the resulting output to be processed would be very similar with this. …
1
vote
Foreign key with multiple references
The comment from @ypercube is right.
You shall model an intermediary table to be able to enforce FKs:
A less formal model, in which FK enforcement would not be possible, could be: