Please define foreign key relationships at the database level so that it becomes impossible to experience the data damage that checklinks is designed to correct.
Comments
The core business logic (the application) would need a major rewrite to do this, over the entire application. If you study the order in which records are added and removed from the database, in all areas of the application, too often "child records" are written before headers or similar that would fail if foreign keys were in place.
This would then have knock on implications for the addon products. However I do agree it would be good to tackle at least the more "risky" tables and drag the schema into the current era.
Could also look at the use of table heaps, lack of clustered indexes too.
Category: System
Administrator
Thank you for your suggestion. This functionality it working as designed, checklinks does a comparision between tables based on the primary keys defined in dex, there is no plan to change this to use SQL foreign keys.
Best regards. This posting is provided "AS IS" with no warranties, and confers no rights.