Re: IBMi --> MS SQL Server Connection

One thing that I did when using this tool was to use it to call Stored
Procedures on SQL Server. In other words, I did not execute a select or
other statement. I did all that work in the Stored Procedure and just
returned the fields. I could be as simple or complex as I needed to be
within the stored procedure. I have some old example code if you are
interested.

On Fri, Jan 12, 2024 at 7:34 PM Javier Sanchez <
javiersanchezbarquero@xxxxxxxxx> wrote:

Thanks Alan, I'll check this and see.

Regards,

JS

El vie, 12 ene 2024 a las 19:16, Alan Campin (<alan0307d@xxxxxxxxx>)
escribió:

I used Scott Klement's JDBC API for several years and it works great.

Both

pulling and updating. Let me know if you need help.

https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://www.scottklement.com/presentations/External%2520Databases%2520from%2520RPG.pdf&ved=2ahUKEwiEyaycmNmDAxVDIkQIHdBlAqAQFnoECCMQAQ&usg=AOvVaw0D6VSlGu68o5ZXmHs0Pmwc

On Fri, Jan 12, 2024, 3:23 PM Jack Woehr via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

There's always JDBC. Ublu <https://github.com/jwoehr/ublu> uses JDBC

to

move data from IBM i to MSSQL.

On Fri, Jan 12, 2024 at 4:20 PM Roger Harman <

roger.harman@xxxxxxxxxxx

wrote:

I vaguely recall doing a POC using the "RDB Connect" product from

DBU.

Never came to fruition in production though.

I know I used to use DBU to manipulate a SQL Server database

running

on a

Windows server. Worked well.

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

--

*JACK WOEHR, IBM Champion 2021-2023
<https://www.credly.com/users/jack-woehr/badges>*

*SENIOR IBM i ENGINEER*

303.847.8442
jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx
<https://www.linkedin.com/in/jackwoehr/> stay connected
<https://www.linkedin.com/company/absolute-performance-inc./>

<https://www.absolute-performance.com/>
www.absolute-performance.com

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain

confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further

distribution or use of this communication is prohibited. If you

received

this communication in error, please contact the sender and

delete/destroy all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.