Hi

If you have done the analysis fully I thing trigger code is less
likely to change than any other area. If your documentation is up to
scratch then everyone should realise they are there! The actual coding
of them is not really very different to any stored procedure.
Therefore I would not be too worried about it.


John

paul_coombes_home@hotmail.com (Paul) wrote in message news:<19ca7866.0310290315.7c552de7@posting.google. com>...
> Thanks John,
> That's pretty much the kind of response I was expecting.
> I just wanted to make sure that I wasn't missing out an alternative
> route.
>
> The only draw-back I can see to using triggers is related to
> maintenance, but that is a draw-back that I can live with.
>
> Paul
>
> paul_coombes_home@hotmail.com (Paul) wrote in message news:<19ca7866.0310280619.211d9fd2@posting.google. com>...
> > Hi,
> > Does anyone have any suggestions on the best to go about enforcing a
> > relationship between two tables that exist within separate databases
> > on the same SQL Server instance.