Our site will have several databases besides the DNN master db.  I've spent considerable time reviewing the DNN core db's schema and would appreciate opinions on the likes of the following:

1) should we leave the DNN master for only core DNN tables and data and for add-on modules that have been "approved"?  In other words, is there a generally accepted rule that says "Don't Mess with the Core Database?"

2) asked another way:  if we wish to capture more data than the core db does, should we keep our extra fields in separate tables?  Even in separate databases?  For example, we want to expand UserProfiles (which are Property/PropertyValue-driven).  Is it ok and common practice to add our own properties and values?  Or, should we not "touch" the DNN tables?   If we shouldn't touch the DNN tables, is it still ok to add our supplemental tables to the DNN core db?  Or, should they live in a totally separate db properly linked (e.g. UserId, UserName, additional data, etc.)

3)  We're also thinking of customizing the "Roles".  If we add new roles in the core db, will checkboxes automatically show up on the many DNN and Module forms for any new roles we add?   If not, how difficult and how risky is it to modify those pages?   (We can accomplish what we're thinking of outside the DNN db if necessary).

Thank you, Sebastian ...  here's what I understand from your reply:

1)  Do NOT touch the schema of any core tables

2)  It's OK to for us to add our own tables, pages, etc. as long as we're extremely careful and don't touch the DNN "core"

3) Many of the DNN features/parameters/options/definitions are designed in such a way that we can easily extend/expand them without messing with the database