Executing against multiple databases (outside Clover Server if possible)

CloverDX Platform
1

Hi
Clover Newbie here. I have gone through the Quick Start Guide, and read through a lot of the documentation, but I can’t find a way to do what I want.
I have dozens of separate SQL databases, all with different hosts and username/passwords. I have a couple of Clover Graphs that I want to run against each database. So I am looking for some way to parameterise this - essentially to loop through a list of database names/hosts/username/passwords, and find some way to feed that to the DB Connection property on a DBInputTable component, and execute each Graph against each database, and create different CSV files for each execution. I don’t see any way to do this with a Lookup or a Parameter. Is there any way to do this outside of Clover Server, which I don’t have?
thanks
Vinny

2

Hi vinny,

Unfortunately, for the specific use case you are describing a CloverETL Server is the only way possible. The DbInputTable is designed to only accept one database names/hosts/username/password in the connection per graph execution. The only way to accomplish your use case would be to build a Jobflow that would create multiple graph executions per database by making use of Parameters (which unfortunately can’t be changed during graph execution).

3

Thanks Pedro, I suspected that might be the case.
cheers
Vinny

4

Hi Pedro
Just to clarify - if I were to use Clover Server, how would I set this up? Would I use a Jobflow, and have a FlatFileReader component to read the multiple rows of connection information from a CSV, and could that then be used to send the connection information into a Graph, to be picked up by the DBInputTable component? I’m playing around with the ExecuteGraph component but I can’t see how to structure this to have one graph being run against multiple databases.
thanks
Vinny

5

Hi Vinny,

That is exactly how I would recommend setting up such a use case. I would create Parameters (ex. Username, Password, Host) in the main graph that contains the DBInputTable and map them using the ExecuteGraph Component. You will also need to use Dynamic Metadata to account for the changes in table structure. Please note that in the documentation that you need to specify a SQL query for the Dynamic Metadata to work properly, this value can be parameterize as well.