English version Russian version

IBProvider news:
2014-06-13 IBProvider 3.20. Improved a support of MS DTS and SSIS. Fixed known bugs.
2014-05-08 IBProvider 3.19.3 and .NET provider 1.0.0.2168 [RC].
2014-01-18 IBProvider 3.19. Changes in metadata schemas.
2013-12-11 IBProvider 3.18. Better support of MSSQL. Changeover to the new VS2012 compiler.
Documentation and samples news:
2014-02-25 [ADO.NET Sample] Parallel transactions within one connection.
2013-12-11 Registration and work with Linked Server of MSSQL 2012.
2013-11-20 Installer for «LCPI .Net Provider for OleDb».
2013-11-15 [ADO.NET Sample] Cancel of query to Firebird. Simple comparison of quality of providers.
2013-11-13 [ADO.NET Sample] Work with native BOOLEAN datatype of FireBird v3 and InterBase v11.
2013-11-12 New samples for "LCPI ADO.NET Data Provider for OLEDB".
2011-01-19 5 key innovations in Interbase XE (Interbase 2010).

IBProvider - OLE DB Firebird driver and Interbase provider

Driver supports 18 Firebird and Interbase server versions:

Connect to Firebird SQL Server

  • Firebird 0.9.4
  • Firebird 1.0 (1.0.3)
  • Firebird 1.5 (1.5.3, 1.5.4, 1.5.5)
  • Firebird 2.0 (2.0.1 - 2.0.x)
  • Firebird 2.1
  • Firebird 2.5
  • Firebird 3.0
  • Firebird 64 bits

Connect to Interbase SQL Server

  • Interbase 4 (4.2)
  • Interbase 5 (5.5, 5.6)
  • Interbase 6 (6.0.1, 6.5)
  • Interbase 7 (7.0, 7.1, 7.5.1)
  • Interbase 2007
  • Interbase 2009
  • Interbase XE (2010)
  • Interbase XE3 (2012)
  • Interbase 64 bits

Moreover, IBProvider supports Yaffil SQL Server work.

IBProvider place among Firebird/Interbase tools and components

... My first test of selecting a few hundred thousand records worked too fast, which initially gave me the impression something was wrong. Upon checking, everything seemed to be fine.

Samuel Davis

... The previous driver we used for interbase would occasionally throw an access violation. There is no way of catching an access violation, so with this previous driver, if we got unlucky our entire application would crash.

As if the driver crashing our entire program wasn't bad enough - occasionally it would return nulls for the first column returned. There was no consistency for these errors and it was impossible to tell what the cause was without debugging into it.

Luckily a workmate referred me to IBProvider... Full case description >>

Best regards,
Samuel Davis
Software Developer
Affinity Team

1. Upgrade to the new versions of Firebird/Interbase will be much more simple.

If you use IBProvider for connecting to Firebird and Interbase, the upgrade to other database server versions as well as the switching between servers will be much easier then in case of using other components.

IBProvider makes automatic setup of its own core to the specific SQL server that includes the following steps:

  1. Defining list of key words, reserved by SQL server.
  2. Loading metadata provider.
  3. Setup of ODBC Escape Sequences parser.
  4. Choice of embedded transactions algorithm and supported dialect.
  5. Connection of algorithms, optimized for concrete database server version.

You only need to write the queries, IBProver will make all the additional work:

  1. Request the information about metadata from SQL server.
  2. Specify the command parameters, their type, precision and size.
  3. Make the correct values transformation to the specified data type.
  4. Upload the data to the own swap-file if their size will exceed the required value in RW memory.
  5. Process Unicode rows in ordinary columns, arrays, BLOB-fields as well as storage-objects correctly

... IBProvider support (I mean it REALLY support) Interbase from the earliest version.

Alessandro Furlanetto

I discovered IBProvider searching google for the best component to use for native Interbase connectivity. I was looking for full Interbase support, smallest footprint and best integration ever. So I was not considering ODBC and I was looking for an OLE-DB/ADO.NET provider.

IBProvider fit the work very well because:

  • It's only one step above Interbase communication library (well not a native .net provider but as mentioned before, ole-db is enough)
  • It support (I mean it REALLY support) Interbase from the earliest version
  • It's well designed (and have a good support forum) so you can install & use or distribuite & use.
  • The data type converter does all for you in a fashionable way.

Since I'm an enough skilled programmer I was trying to save me some pain in the ass choosing the right provider. IBProvider is far above what I need so I choose to tell my customer about it. This is because if I do a good job I like to be acknowledged for that and the same apply for software solutions that I use.

I'm a consultant and a software developer. I wish to thank you for such a great product. I want to say also that I'm not interested in winning the prize, it's enough to witness how I like IBProvider. Full case description >>

Best regards.
Alessandro Furlanetto,
Italy

In IBProvider we try to take into account all the nuances of Interbase и Firebird API implementation, covering them with standard OLE DB interfaces. It helps working with Firebird and Interbase, usage of client libraries OLE DB, ADO, dbGo (ADO Express), ADO .Net, as well as some others.

2. A wide selection of development tools for interaction with Firebird and Interbase.

OLE DB providers technology is supported by practically all the modern development tools. Among them:

  • Report builders: Crystal reports, Fast Reports, Reporting Services (SSRS).
  • Analysis and OLAP tools (Analysis services (SSAS)).
  • Microsoft Office applications (Word, Excel, Visual Basic For applications (VBA)).
  • Microsoft SQL Server 2005 Linked Server and Business Intelligence.

ADO Library

It enables developing applications in Visual Studio 6.0 (5.0) Visual Basic, Visual C++, as well as writing automatization scripts for Windows Script Host (WSH) on VBScript and JavaScript.

ADO.Net Library

You may use IBProvider and ADO.Net for connection to Firebird and Interbase in Visual Studio .Net 2008, 2005, develop modern applications on C#, Visual Basic .Net and other languages.

In ADO.Net Library there is a large set of components for the work with data: DataGrid, DataView, TableAdapter, OLE DB components, built-in masters and utilities (Server Explorer, Data connection wizard, DataSet designer) and other tools.

Client library on C++ for OLE DB

It enables to develop the applications on C++ in Visual Studio 2005(2008) and in С++ Builder. IBProvider is spread free of charge as the part of distributive.

Delphi and C++ Builder

The access to Interbase and Firebird from Delphi or from C++ Builder you may choose among the following variants::

  • Interact with ADO via COM interfaces.
  • Use dbGo (ADO Express) components.

Moreover, for C++ Builder you may use C++ library from IBProvider distributive free of charge.

MS SQL Server 2005 Business Intelligence

IBProvider enables working with Interbase and Firebird not only via the MS SQL Linked Server but also as the component of Business Intelligence tools:


... with IBProvider we solved the problem of data lost in the course of transfer to the new Firebird-based information system

Roman Viktorovich Budzilo, TelekomPlus, Perm

In 2010, our company had its 15-year anniversary. The top management decided to purchase a ready-made and polished by years information system that will cover most business areas.

The upload took place. Oh, God! Some imported data was distorted or lost. How were we to find the difference, taking into account that the source data was on MS SQL Server and the target DBMS was FireBird. After the linked server had been created, we discovered that the ODBC driver was unable to cope with quite large amount of data, we are not talking about millions of entries, just several dozens of thousands. The queries directly merging data from the two DBMSs were run disastrously slowly.

We decided to test IBProvider. Wow! The same query was run in several seconds. We couldn't believe it, it was perfect! We compared the data and corrected the differences. Moreover, we decided to transfer the new information system to new x64 server. We though this provider was not suitable for x64. Nevertheless, we read instructions and tried. And it worked! Full case description >>

Roman Viktorovich Budzilo
Head of information systems development and support department
ZAO TelekomPlus, Perm

3. Possibility to work with 32-bit and 64-bit applications.

IBProvider Professional exists in 2 editions:

  • IBProvider Professional Edition for 32 bits - a standard version allowing to create 32 bits applications.
  • IBProvider Professional Edition for 64/32 bits - a component package allowing to develop 32 bits as well as 64 bits applications.

4. You don't have to reinvent the wheel, all you need for work is already available!

Valuable transactions support

  1. Embedded transactions.
  2. Distributed transactions, two-phase commit, MS DTC transactions coordinator support.
  3. Transaction retain (Commit Retain/Rollback Retain).
  4. Transactions auto commit mode.
  5. All the isolation levels: read committed, snapshot, Snapshot Table Stability.
  6. Named Savepoints.

Work with commands parameters

  1. Named and positional parameters support.
  2. Automatic specifying of parameters descriptions, data sizes, precision and types.
  3. Direction Support - In/Out parameters.

Data types

  1. Support of all the Interbase and Firebird data types, including arrays and BLOB-fields.
  2. Support of special types like BOOLEAN in Interbase 7, Interbase 2007, Interbase 2009
  3. Emulation for BOOLEAN and GUID types in Firebird and in Interbase before Interbase 7.
  4. Implementation of the wide OLE DB Types range.
  5. Built-in types converter (client errors protection).

SQL queries parser

  1. Support of SQL-scripts
  2. Special support of DML for Firebird 2.0, Firebird 2.1 (MERGE, UPDATE OR INSERT, RETURNING, EXECUTE BLOCK, etc).
  3. ODBC Escape Sequences parser.
  4. DDL queries support (CREATE/ALTER/DROP).

Also

  1. Connection pool support.
  2. Query pool support.
  3. Updatable Rowsets and Bookmarks support.
  4. Work with multithreaded applications.
  5. new!Asynchronous rowset loading, which can give up to 30% to speed of data processing.
  6. Client and server cursors support.
  7. Support of 49 Firebird and Interbase code pages, including UNICODE, UTF8 and binary OCTETS.
  8. Multilingual support and built-in connection wizard - Microsoft Data Link.

5. Saving of application development time.

IBProvider is a big choice of development tools and support of all the Interbase and Firebird servers. Don't waste your time studying the low-level Firebird and Interbase API. Don't learn the components that limit you in choosing the development tool, download IBProvider.

You can find the answers to the majority of questions in the detailed documentation chapter and on forum.


... In our tests, the transaction execution speed for a table of 4,500,000 was only 9 seconds compared to 13 seconds for the same Delphi query

Igor Horev, Samara horizons

The 3 main reasons for choosing IBProvider were the following:

  1. The transaction execution speed for a table of 4,500,000 was 13 sec for a Delphi query and 9 sec for a IBProvider query (this was the test to ground the purchase of the product).
  2. Economical resource consumption - possibility of parallel work with other database filling Delphi programs.
  3. Crucial for the decision to buy IBprovider was the ability not to interfere with our company's main product - Volga hardware and software complex.

Full case description >>

Regards,
Igor Horev
Samara horizons.


Native OLE DB Provider OLE DB for InterBase OLE DB for Firebird


Next