DDE to SQL DB bridge

[grikag]

Hello Chris, I hope you are well. I came across your free MS Windows - DDE tools and was very impressed by the variety of the options they support. I am not a developer, like you :) and reaching out for guidance or help, accounting your expertise.

Considering the integration DDE / RTD options for capturing data, a) supported by the legacy desktop application and b) controlled by the vendor, I am searching for the "DDE / RTD to Database (SQL Server)" bridge.

with added options,
-- input-config //per your manual example, listing all data requests in the file
--server REUTER --topic IDN_RWS --item "GBP=,BID ASK"
--output-config // listing file or the database destination parameters

Was hoping you might have such a tool (feature) planned or may recommend open source references.

Please forgive me for disturbing you, I am not trying to take advantage of your time.

Kind Regards, GK

[chrisoldwood]

I am inclined to see this as a new tool rather than an extension to DDECmd mostly because it'll likely have a bit of variation to deal with different SQL sources & sinks. Given it's intended use case I'd also need access to a (financial) tool that can generate DDE data at a fair rate of knots as I no longer have access to Reuters and Telerate like I used to.

I'm happy for any ideas and thoughts to be collected in this thread in the meantime.

[grikag]

I have located the following project that looks very complex and had no updates for 4+ years. https://github.com/jeog/TOSDataBridge

I see few options for the solution implementation:

a) Simple data bridge, connecting DDE/RTD server with subscriber repository. b) (a) + added REST API integration support c) (b) + support for output format (e.g., CSV, JSON, XML) d) (c) + integration with NoSQL destination db like MongoDB

Added "source" and "destination" configurations should help with maintaining bridge instance"
a. DDE or RTD "subscription" to the source can be preconfigured (re: request file) with map of items vs topics b. Listing "destination" properties (e.g., "type": file .., "name:x , path:x , etc.)