9 replies
by pvp
Your question is a bit terse, but...
If you're trying to verify x.table against y.table, the trigger on x.table can do that easily.
If you're trying to ensure the integrity of y.table, you need a trigger (maybe even the same one, or with minorchanges) on y.table.
Remember, triggers are invoked by *attempted* operations on a table, and operations on y.table will not invoke the trigger on x.table *unless* y.table has a trigger that (a) invokes the x.table trigger or (b) does some operation on x.table.
by gibs42
by roc180
I think you want to know how to cross databases. If thats the case in your database X table x1 trigger code make sure you fully qualify the table y1 in database Y. To fully qualify table y1 use the syntax Y.dbo.y1 in your SQL. If Y is on a different server you will also have to include the server name or its alias.
Neal Martinelli
by gibs42
by john_bosko
by gibs42
by ohjani
In your trigger, replace the database Y name to
..dbo.
by gibs42
by gibs42
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending