Pulling from two databases

[routledge]

Good morning, good afternoon or good evening all

I have a real issue and would appreciate feedback. I am attempting to link two seperate databases on seperate servers and link to them from ONE installed version of sugar.

Now i'm not looking for a step by step tutorial (I can do that later for you guys if I decide to develop my system), I just want some feedback on what files to pitch for and if you believe it will be possible.

Anyway thanks for looking

Regards

John

[andopes]

Hi John

It is good morning for me!
Some questions:
1. What kind of data there are in these database? Same as in sugar database?
2. Do you want to enable sugar to join to two databases?
3. Do you want to sync the two database to the database under sugar?

Cheers

[eNick]

John,

The easiest way to achieve what you wish to do (and manage all of the problems such as de-duplication, determining which is the master if there are any conflicts etc). Is to use an off the shelf ETL (Extract, Transform, Load) tool such as:

Jitterbit www.jitterbit.com
Talend www.talend.com

Both are Open Source tools available for free with support for the databases used by SugarCRM. You can then link the databases via a drag and drop interface and manage any complex transformations.

Talend recently gave an excellent presentation at the SugarCRM Acceleration Summit in London.

If rather than merge databases, you're interest is in persuading Sugar to dynamically switch between two disperate databases, this can be done by adding code to config.php or config_override.php to change the definition of the database connection depending on, for example, a session variable.

If you're using Pro, however, be aware that there are licensing implications as the license only allows for one production and one development/backup database - not two production databases.

[routledge]

Thanks fellas

First to eNick as i'm looking into the software you have described. Secondly to Andropes who is becoming a true savior.

The problem I have is that the data in the external database (not sugar) is configured in a vastly different way to sugar. It manages most of the queries and other data on the database side. This is making the use of federated tables a nightmare to impliment. We have tried using API's for everything we want to query but this also could take an age to do. So that is why we may be looking to patch into both databases at the same time on a module by module basis to keep the i.e. each module will access there own tables within another database. Hope this is enough info...

Regards

John

[routledge]

Further to Androples

Connect sugar to two databases, would probably be the best

Regards

John