Thread: To Create or Not to Create multiple backends

Quote: Originally Posted by gemma-the-husky ..... what i think he has, is a SEPARATE backend database for EACH table, because he is concerned about the 2GB limit Is that approach not going to complicate the task of maintaining referential integrity?

only when I create query that needs relationship I create relationship between tables. I do not establish Referential Integrity.

Quote: Originally Posted by genesis May I ask if you have problems with RI there or how did you establish your RI? I mean did you enable your RI? Was you database working fine with or without RI? Did you have integrity issues? I always enforce RI. If I can let the database engine do it, that is the easiest and IMHO the best way. So whenever possible , you keep all tables in a single database that are getting data entry from the users. As the...

Quote: Originally Posted by HiTechCoach I figure that was the case. I was responding to the fact that you think your databases have been working just fine. I was recommend that you take a copy of your database and create all the RI relationships. If you can enable RI, then your database was working properly. If not, then your database has integrity issues. yes I have tested it without the RI and I created query and codes and it work just fine...

thats what i said, among other things - but he seems determined to continue in this way ... i may have it wrong, but thats what it seemed to me. i thought the "front end" he was using was more designed to provide a single interface to a group of databases, but i got the impression he was using it in a different way, as above

If the tables are growing to the extent that they all need separate databases, isn't that an indication that they might grow further so that some of them may individually become too large? If it's important enough to be planning by splitting them all out, I think it's important enough to deserve migration to a more powerful DB solution.

Quote: Originally Posted by genesis I do not establish Referential Integrity. Why not? It makes it easy to ensure you don't get a mass of orphaned records which can adversely affect performance. And as you have already said a relational DB should enforce RI.

If the tables are growing to the extent that they all need separate databases, isn't that an indication that they might grow further so that some of them may individually become too large? If it's important enough to be planning by splitting them all out, I think it's important enough to deserve migration to a more powerful DB solution.