TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Master Database/Child Databases
So we have a consulting business that serves a particular vertical market. we have done a excellent job in selling our DB as a value add so our customers can see what is going on in their business. These business are all independently owned, and each has there own instance of our DB. I would love the ability to have a master/child DB for multiple reasons.

1- I have multiple tables that are identical in 14 other DB that would be great that I can make one modification and it is for all DB instead of changing in 14 different DB when I need to change 1 number

2- As we consult for all of these I would love to be able to build Views that would role up the data from all 14 to be seen only by our consulting business in a "Master" DB

3 - these business are very information sensitive even though they are not direct competitors we obviously sign NDA's with them and cannot make one master database and restrict view by area as the liability is to great for someone accidentally seeing wrong data

4- contrary to the above statement there are times where on dealer will request another do service work for them and it would be great to be able to pass data between DB's

My initial thought behind this was to create a trigger that could create records in a different database but have been unable to come up with a way to do this.

Looking for ideas that I haven't thought about???


Mike Nelson
Date Created
9/11/2018 11:46:37 AM
Date Updated
9/18/2018 3:00:42 AM
New Idea
Promoted By
Patricio BustosDale OliverMike Nelson
Scott Miller 9/11/2018 12:10:07 PM
@Mike have faced a similar challenge and at the record level it is possible to use the API to sync databases which works well but there are some limitations.

1. You can't pass actual attachments via the API (as far as I'm aware).
2. In order to prevent cyclic references (endless loops of updates) the easiest solution is to disable workflow triggers when using the API. The issue with this is that most databases rely on workflow triggers so you have to be mindful they wont run in that situation. You can use time dependent triggers as a workaround but they are not as elegant.
3. It only covers the data. Any changes to the database setup are not replicated

In the end we opted for a single database and paid special attention to access/privileges and Unique identifiers. Synching multiple db's could prove quite time consuming
Philipp Matuschka (MMB) 9/18/2018 3:00:42 AM

I have a single database with multiple clients using it. For each table there is a column which defines which client can access the record. this is then built into record access rules. It has been working for 3 years now without any issues.

If you want to see it from a user end, sign up for a free trial from

Back to Search Results