ADO .NET and Informix
Hello Friends, We are scoping out a project to replace a component of an old school, legacy application written in ESQL with a .NET service based application. To this end, wondering if anyone here has had any experience with using .NET and Informix together. All anecdotes are welcome. Specifically, wondering if anyone knows of any caveats in using ADO that would potentially save me time, and/or, cause me to look in a different direction. As always, thanks for you time in reading and replying. Cheers, Tam.
We are considering doing the same thing. Just beginning design and coding. I would suggest using the generic .NET ODBC classes (we are using the ver 2.90 odbc driver) instead of using the .Net wrapper provided by the Informix CSDK. Apparently it uses OLEDB which causes many performance issues because of COM interop overhead (alot of "unmanaged" code). Also, I suggest you perform a major stress test early in the development stage of your project. There were some memory leak problems with the informix ado drivers in the past, they seem to be cleared up but its much better to find it now then once you get into a production environment. Basically you want to run a couple million queries against the informix box through the odbc driver, then make sure the db mem didnt grow massively and then blow up or slow to a crawl. GL Tam OShanter wrote: > Hello Friends, > > We are scoping out a project to replace a component of an old school, legacy > application written in ESQL with a .NET service based application. > To this end, wondering if anyone here has had any experience with using .NET > and Informix together. > > All anecdotes are welcome. > Specifically, wondering if anyone knows of any caveats in using ADO that > would potentially save me time, and/or, cause me to look in a different > direction. > > As always, thanks for you time in reading and replying. > > Cheers, > > Tam.
I have observed that Informix .NET provider gives better performance than that achievable by using ODBC-NET bridge. Also , AFAIK , the NET provider does not use OLE-DB under wraps. As Zackary said , a lot of problems with the .NET provider have been getting cleared up with the latest releases and hopefully the trend should continue. --- zackary.evans@gmail.com wrote: > We are considering doing the same thing. Just > beginning design and > coding. > > I would suggest using the generic .NET ODBC classes > (we are using the > ver 2.90 odbc driver) instead of using the .Net > wrapper provided by the > Informix CSDK. Apparently it uses OLEDB which causes > many performance > issues because of COM interop overhead (alot of > "unmanaged" code). > > Also, I suggest you perform a major stress test > early in the > development stage of your project. There were some > memory leak > problems with the informix ado drivers in the past, > they seem to be > cleared up but its much better to find it now then > once you get into a > production environment. Basically you want to run a > couple million > queries against the informix box through the odbc > driver, then make > sure the db mem didnt grow massively and then blow > up or slow to a > crawl. > > GL > > Tam OShanter wrote: > > Hello Friends, > > > > We are scoping out a project to replace a > component of an old school, legacy > > application written in ESQL with a .NET service > based application. > > To this end, wondering if anyone here has had any > experience with using .NET > > and Informix together. > > > > All anecdotes are welcome. > > Specifically, wondering if anyone knows of any > caveats in using ADO that > > would potentially save me time, and/or, cause me > to look in a different > > direction. > > > > As always, thanks for you time in reading and > replying. > > > > Cheers, > > > > Tam. > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >