Mr. Hartmann wrote on his blog
Last week, I posted a story about my interaction with a software developer who uses FireBird (FB) as a back-end for their software. The short version is that they left FB’s settings at default and were using a really, REALLY old version of FB. This caused the application to have massive (18 minute) load times and hang the entire server, with just one client connected. Bellow (in the article) are the changes I made to increase overall performance of the application and server.
News via Patrick Pierson‘s blog
I found this link on reddit under /r/sysadmin. Josh Hartmann has a customer that had slowness issues with a database server. Josh contacted the developer and every time the developer’s response was to add more hardware to the problem. After some investigation he found a few issues with the developer’s setup of the server, fixed it and now his customer is happier then ever. Here is his write up, great stuff.
We are pleased to announce the second release candidate of our .NET Data Provider for interaction with Firebird and Interbase via IBProvider. By now, we have implemented all the functionality of System.Data.OleDb.
If you want to transfer your .NET projects for FB/IB to the new level of functionality and quality, we recommend you to start using «LCPI .NET Data Provider for OLE DB».
Just look of this DDEX screenshot:
You can get more screenshots and download Ole Db .Net Provider for access to any Interbase or any Firebird database from ADO.Net here: OleDb .Net driver for Firebird >>>
I’m pleased to announce new version of .NET provider. You can read more at http://blog.cincura.net/233471-ado-net-provider-4-5-0-0-for-firebird-is-ready/.
ADO.NET provider 18.104.22.168 for Firebird is ready and you can find more at http://blog.cincura.net/233462-ado-net-provider-4-2-0-0-for-firebird-is-ready/.