15 + years Solutions-oriented Integration Interface Specialist with notable success directing a broad range of corporate IT initiatives while participating in planning and implementation of Integrated solutions in direct support of business objectives. Specialties: Design/Development of MS and Oracle SQL Databases, HL7 Ancillary Solutions, and Intersystem Ensemble Solutions. Integrating it all together to create a more robust environment.
While working with Intersystems Ensemble and now IRIS, I have greatly expanded my knowledge of Ensemble and Cache Object Script by asking questions and watching the Developer Community. I tend to ask questions, then figure out the answers on my own or with a little help from others.
Before Intersystems Ensemble, I spent many years as an eGate developer. Specializing in DART, JDBC, and other out of the normal odds and ends.
What do you suggest I use instead?
Yes, the "xxxxxx" represent the SQL Connections, however we must maintain 3 different connections as there are 3 different environments we send data to in MS SQL.
Yes, the code should be the same, but there are times where we are testing things in DEV before they go to the TEST MS SQL environment.
Modifying the SQL Connection String at the System level isn't as logical.
I thought it would be easiest to define the Linked Stored Procedure once and just update the Connection String within the Object Script when I was ready to move it to a different MS SQL Environment.
Were you ever able to figure this out?