Re: Orphaned tupels, should I clean or is it ok to leave?

I can't help but comment here.

We're implementing a 3rd party CRM package, and the software treats the
database like a big pile of stupid ascii files.  There's no RI - no FK's
in the tables.  NULLs are allowed everywhere...   When a PK is deleted,
rather than cascade delete, it looks like any logical references to it
are simply set to null..

Its enough to drive a DBA completely freaking insane...

Is this sort of thing common in CRM packages?

aj

--CELKO-- wrote:
>>> If I was to leave these as they were and set constraints with NO CHECK
is it likly that I am going to run into problems down the track?  <<
> 
> oh yeah!  The schema will fill with garbage and will choke.  Someone
> will use the meaningless data for a re****t, etc.