Has anyone connected a DB protocol to AZURE? or AWS?

[Peter Heggie]

We were asked to send data directly into an external database. Never did this before. We do have a VPN.

I assume that we would work with our network group, and theirs, to identify a NAT’ed server name that we can use in our database connect string.

I will assume that we would INSERT to a staging table. Not sure if we can copy from a local table to an external table with an INSERT INTO … SELECT * FROM.. syntax; it seems that the outbound protocol is message-based. Maybe we should use a DBLOOKUP in a tcl instead of using the DB protocol – the DBLOOKUP should let us do more with SQL.

I am reluctant to implement this with a real-time interface, and prefer to setup a batch schedule when this interface will be enabled, but maybe there is little need to be cautious about being connected to a cloud service 24×7?

Is there any experience out there in this area?

Thanks, Peter

Peter Heggie

Topic

[Jim Kosloskey]

I have never done this but I would think if the DB can be made addressable to the Cloverleaf platform it would be no different than any other DB.

Assuming the contract with the owner of the DB has assured service levels that match any in-house system’s I would think there could be some level of confidence overall performance will be no worse than in-house DBs. Thus real-time should not be a big issue.

A staging table is the best methodology in my mind with any DB integration involving modification to a DB for a number of reasons. As a matter of fact, when I did the DB Integrations at MDACC, I insisted on that architecture.

I hope you get a response from someone with some real world experience in this though.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies