Reading from AS400 [modified]
-
Hello, Which provider should I use for transferring data from as400? I cannot use Microsoft provider as I am using standard edition. As for IBM providers there are three ones for native ole db: IBM db2 udb for iseries ibmda400 ole db provider IBM db2 udb for iseries ibmdasql ole db provider IBM db2 udb for iseries ibmdarla ole db provider and there are the same three for Ado.Net Apart from ole db I can use ODBC and use the DNS I have created in data sources. Which one will be the fastest? I believe using native will be better but which one from the three possibilities? Also, are there any gotchas to take into consideration? Any tips and tricks? Thank you.
Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion
modified on Saturday, February 7, 2009 6:24 AM
-
Hello, Which provider should I use for transferring data from as400? I cannot use Microsoft provider as I am using standard edition. As for IBM providers there are three ones for native ole db: IBM db2 udb for iseries ibmda400 ole db provider IBM db2 udb for iseries ibmdasql ole db provider IBM db2 udb for iseries ibmdarla ole db provider and there are the same three for Ado.Net Apart from ole db I can use ODBC and use the DNS I have created in data sources. Which one will be the fastest? I believe using native will be better but which one from the three possibilities? Also, are there any gotchas to take into consideration? Any tips and tricks? Thank you.
Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion
modified on Saturday, February 7, 2009 6:24 AM
Have you checked this: http://www.itjungle.com/fhg/fhg050306-story02.html[^] "IBM offers the OS/400 community three OLE DB providers: IBMDA400, IBMDASQL, and IBMDARLA. As a review, IBMDA400 is a general purpose, all encompassing provider that supports SQL, command and data queue interfaces. IBMDARLA is the record level access provider and is primarily for applications that work with single records instead of sets of records. The IBMDASQL provider was released with iSeries Access V5R3 and is an SQL only provider."
The need to optimize rises from a bad design.My articles[^]
-
Have you checked this: http://www.itjungle.com/fhg/fhg050306-story02.html[^] "IBM offers the OS/400 community three OLE DB providers: IBMDA400, IBMDASQL, and IBMDARLA. As a review, IBMDA400 is a general purpose, all encompassing provider that supports SQL, command and data queue interfaces. IBMDARLA is the record level access provider and is primarily for applications that work with single records instead of sets of records. The IBMDASQL provider was released with iSeries Access V5R3 and is an SQL only provider."
The need to optimize rises from a bad design.My articles[^]
Thank you Mika. I will only need to issue select statements so I guess IBMDASQL will be most efficient.
Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion
-
Thank you Mika. I will only need to issue select statements so I guess IBMDASQL will be most efficient.
Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion
Giorgi Dalakishvili wrote:
I will only need to issue select statements so I guess IBMDASQL will be most efficient
Yes, I also think that would be a good choice when using selects only.
Giorgi Dalakishvili wrote:
Thank you Mika
You're welcome :)
The need to optimize rises from a bad design.My articles[^]