topic Re: Create different db connection for each db partition in SAS Customer Intelligence

Create different db connection for each db partition

teresa_abbate — Wed, 12 Oct 2016 14:13:02 GMT

Our db has two different partition: One for Outbound campaign table and one for Inbound campaign table.

CI is configured for the outbound partition connection. It is possible create an other connection for sas Customer Intelligence that references the inbound partition?

Thanks,

Teresa

Re: Create different db connection for each db partition

shill — Wed, 12 Oct 2016 15:46:52 GMT

Can you please clarify your situation a little for us? What database are you using, and when you say "partition" do you mean "schema" or a totally separate database instance?

Re: Create different db connection for each db partition

teresa_abbate — Mon, 17 Oct 2016 11:05:21 GMT

We work with an Oracle DB which has 3 istances and 3 differents service names.
It is possible specify differents service names for outbound campaign connection and inbound campaign connection?

thanks,

Teresa

Re: Create different db connection for each db partition

shill — Mon, 17 Oct 2016 14:02:19 GMT

While all of your data sources for MA (outbound campaigns) should be using the same connection (in other words, even if you have multiple libraries included in one information map the only allowable difference between them is the "SCHEMA=" parameter), every data process used by RTDM (inbound campaigns) is executed separately, so the data can come from any (supported) connection.

Re: Create different db connection for each db partition

teresa_abbate — Mon, 17 Oct 2016 14:38:15 GMT

do you mean that RTDM connection uses only the jdbc connection resource configured on the decision services for reading db tables?

In this case, it' enough changing the service_name in the resource's server url.

Re: Create different db connection for each db partition

shill — Mon, 17 Oct 2016 14:47:46 GMT

For a data process during execution, yes - it only uses the JDBC connection resource's definition, so you should use that point to the database you'll be using for real-time (hopefully a different database than one used for batch applicaitons like MA!). It uses the SAS library that goes with that (connected by matching the name of the Library System Resource) when you're creating a definition - that's where it gets the metadata to define the criteria and retrieval variable names.