|
ODBC is the Microsoft connectivity standard and has nothing to do with DRDA. DRDA is the IBM connectivity standard. The only "DRDA" compliant databases I am aware of are DB2 (PC, Server, Linux, Unix, iSeries and Mainframe) and Informix. Oracle and Sybase both have DRDA connectors as options. DB2 is ODBC compliant as a server, not as a client. Microsoft does not have a DRDA connector, but you can use ODBC or JDBC to connect "FROM" a MSSQL server to a DRDA database. John Brandt iStudio400.com (903) 523-0708 Home of iS/ODBC - MSSQL access from iSeries and RPG. -----Original Message----- From: CWilt@xxxxxxxxxxxx [mailto:CWilt@xxxxxxxxxxxx] Sent: Tuesday, November 09, 2004 12:19 PM To: midrange-l@xxxxxxxxxxxx Subject: RE: SQL SERVER/ISERIES INTEGRATION Yep, basically like DDM. DDM is the iSeries client side implementation of DRDA. The iSeries can be both a DRDA server and a DRDA client. DRDA is an open standard for accessing remote DBs. OBDC is a result of the perversion of the DRDA standard. SQL server, among others can be DRDA clients but not DRDA servers. So in SQL server, a linked table is a DRDA connection from SQL server to the iSeries. HTH, Charles Wilt iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 > -----Original Message----- > From: Elvis Budimlic [mailto:ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx] > Sent: Tuesday, November 09, 2004 1:00 PM > To: 'Midrange Systems Technical Discussion' > Subject: RE: SQL SERVER/ISERIES INTEGRATION > > > I haven't had a chance to actually use SQL Server, so I plead > full ignorance > on "linked server" setup. Is that like DDM? > > -----Original Message----- > Subject: RE: [SPAM] SQL SERVER/ISERIES INTEGRATION > > Elvis, > > The problem is the original poster is inserting from an SQL > server via a > "linked server". > > So she's not going to have the control over the connection > she would via > ODBC/JDBC. > > Charles Wilt > > > -- > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.789 / Virus Database: 534 - Release Date: 11/7/04 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.789 / Virus Database: 534 - Release Date: 11/7/04
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.