Re: DRDA and Azure SQL Server -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: DRDA and Azure SQL Server
From: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Date: Mon, 7 Feb 2022 09:11:02 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Details! Requests to the data host servers, now if those have to be DRDA, I don't know, I might have to look into that someday!

Anyone sure about what the host servers want to see?

Cheers
Vern

On 2/7/2022 8:32 AM, Patrik Schindler wrote:

Hello Vern,

Am 04.02.2022 um 19:45 schrieb Vern Hamberg via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:

DRDA is like ODBC, you need an application that uses the DRDA functions to work with data remotely.

Ehm. No. ODBC is a pure client side API, while DRDA is a specification including the wire protocol.

As far as I've understood, DRDA is indeed what's flowing between an ODBC client connecting to the "ODBC port" of the *DATABASE host server.

:wq! PoC

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.