SEO

#1 (**permalink**) 02-28-2008, 06:33 PM

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.

#2 (**permalink**) 02-28-2008, 06:33 PM

Hi

You could do this using a instead of trigger or using a check constraint and
function. The latter may not perform that well.

John

"Paul" <paul_coombes_home@hotmail.com> wrote in message
news:19ca7866.0310280619.211d9fd2@posting.google.c om...
> 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.

#3 (**permalink**) 02-28-2008, 06:33 PM

Hi

The second query should show them, but the problem would be that all
possible combinations will be shown.

As there is not a fixed number of exams that may be either the min or max,
the best solution is to do the transformations on the client.

John

"Paul" <paul_coombes_home@hotmail.com> wrote in message
news:19ca7866.0310280619.211d9fd2@posting.google.c om...
> 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.

#4 (**permalink**) 02-28-2008, 06:33 PM

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.

#5 (**permalink**) 02-28-2008, 06:35 PM

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.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Table relationships