What I meant to say is, you can use separate databases for tables that are unrelated. That way RI code and SP code are stored in a separate .dbc. This doesn't mean anything really other than when a developer looks at a project he can easily see what rules apply to what tables by studying each dbc separately. However, if all or most of your tables are subject to many of the same rules and procedure this would not be an advantage from a development standpoint.

HTH