IBProvider - news, releases, manuals

The new IBProvider 3.9.4 improves compatibility with .NET. Fixed known bugs.

The release of this version was preceded by a great amount of work on the analysis of the interoperation of IBProvider and .NET.

This resulted in the following changes:

If the required initialization properties are not specified, the connection ends with the code E_FAIL (connection error), but not with DB_E_ERRORSOCCURRED, which meant though erroneous but established connection.
Now, you can use single quotes in the connection parameter string.
We detected and eliminated the memory leaks in IBProvider. If you haven't done it yet, we recommend you to upgrade to the latest version.

Do you want to develop fast, reliable and compact applications
using the capabilities of the latest versions of Firebird and Interbase?

Choose IBProvider Professional v3.9.4

Download it right now!!!

Or purchase the time-unlimited personal license

New IBProvider v3.9.1 become more faster.

New IBProvider v3.9.1 become more faster

We are continuing to improve IBProvider performance.

In the current version:

IBProvider x64: the initialization property Window Handle has the type VT_I8.
The algorithms for working with random access memory were once again optimized and improved, which again testifies that there is no limit to perfection. In addition, the latest versions of the algorithms use new capabilities of C++0x for working with RAM.
The new IBProvider x64 is compiled using Visual Studio 2010 SP1. The updated version of CRT: 10.0.30319.460.

Do you want to create quick and compact applications
using the capabilities of the latest versions of Firebird and Interbase?

Choose IBProvider Professional v3.9.1

Download it right now!!!

Or purchase the time-unlimited personal license

The new version of IBProvider v.3.9 is delivered with the warranty(!) of stable performance within systems operating around the clock.

The new version of IBProvider 3.9 is delivered with the warranty(!) of stable performance within systems operating around the clock

Do you trust your access components for Firebird and Interbase as much as to allow them to be active without monitoring within software systems operating around the clock?

Maturity of a software system is defined by its ability to operate smoothly without monitoring for a sustained period of time.

You can close your eyes to the fact that:

many “programs” have to be restarted several times an hour because of memory leaks, deadlock, as well as unexpected critical errors which close your application, say, ten minutes after you have typed an unsaved text.
when working with large amounts of data you have to watch for several hours at the frozen application window, hoping that this report will nevertheless be read to the end, only to come early next day and see the “Out of memory” message instead of a ready analysis

The worst thing happens when the reason to these problems is not your code, but the selected access components for Firebird and Interbase.

Over 10 years of development and testing of access components within round-the-clock systems for processing large amounts of data, have taught IBProvider managers that mature access components must employ the “maximum client error tolerance” approach, instead of the common approach “this is your fault, you should have thought what you were going to transfer to your server”.

On the one hand, a usual driver can only be a layer between a database server and a client application and translate everthing that is transferred from the client to the server without any processing. This approach entails the problems described above:

suspensions,
memory overflow errors,
critical errors leading to a loss of all unsaved data,
conversion errors as well as the so-called “magic” errors of the server.

The maximum client error tolerance approach involves the following:

A strategy of preventing any problem and repacking any client queries into the form compatible with Interbase and Firebird.
Possibility of processing any amounts of data of any type (texts, videos, images, super arrays etc.).
Automation of routine developer operations such as:
- automatic description definition of instruction parameters.
- generation of update, delete, insert instructions based on select instruction.
- possibility of a batch execution of queries to a database in a single instruction (SQL-scripts).
- monitoring of memory overflow and roll-out of too large data into a separate SWAP-file on the local drive.
Execution of functions which are not available on the server at the level of IBProvider.Including:
- nested transactions
- Boolean data types and GUID even for the most outdated server versions
Automatic detection of the server type and its configuration:
- definition of the list of keywords reserved for the RDBMS.
- configuration of metadata loader.
- configuration of the parser of ODBC Escape Sequences.
- selection of nested transaction algorithm as well as a supported dialect.
- connection of algorithms optimized for a specific version of database server.
- and a whole range of individual settings which might still be unknown to IBProvider users.
User-defined conversion of data types. While testing IBProvider we had to change many server scripts by our own ones, including the type converter.

So the new version of IBProvider 3.9 provides a fault tolerance which offers:

New fail-safe algorithms for processing large arrays. For example - CHAR(30000) [-32000:32000,-32000:32000]. Optimized read/write operations for arrays.
New fail-safe algorithms for processing 4 GB BLOB fields under 32-bit Windows.
Correct support for 4-byte UTF8 symbols (processing of substitution symbols, extended size of WSTR-columns).
Enhanced UNICODE_FSS support. Absolutely new scripts of conversion to UCS2 and vice versa.
Patch for the error caused by .Net Transaction Scope and “Unsupported Isolation Level”. Now in case there is an UNSPECIFIED isolation level (-1), the provider will use an isolation level which is defined for the entire distributed transaction. Please note that by default TransactionScope uses SERIALIZABLE isolations. The other isolation level can be defined through TransactionOptions.
Patch for the error caused by processing textual arrays and NONE code page.
New 64-bit version assembly of IBProvider is implemented using the VS. Net 2010 compiler which provides a more efficient and smaller code. This is another reason to think about smooth transition to 64-bit applications.

We do not have time for manual testing of all working options of IBProvider that is why we conduct 1.44 million tests automatically

You might have noticed that IBProvider is regularly tested which helps fix critical errors which do not occur to a developer until they actually happen: data types, encodings, transactions, large amounts of data, multiple threads, maximum allowed values - all of this is to be automatically tested.

You would agree that it is better to foresee as many options as possible while texting access components instead of making your own collection of “what should not be done” while exploiting round-the-clock systems which are liable to terminate with a critial error without any explicit reason.

From June 11 through July 19, 2011, we conducted an intense multithread testing of IBProvider and Firebird:

System: Vista x64, Q6600, 8GB, RAID10 (4xWD RE3 1TB)
IBProvider: x64, v3.8.2.12727, compiler: VS2010
Firebird: x64, v2.5.1.26308, SuperClassic, compiler: VS2008
Tests: IBProvider Test System, 8 Threads.

Both the provider and the server passed 1.44 million different tests without any errors.

In conclusion, We would like to ask you the same question which was put up at the beginning of the article:

Do you trust your access components for Firebird and Interbase as much as
to allow them to be active without monitoring
within software systems operating
around the clock?

Get you new fail-safe IBProvider right now !!!

In addition to the latest driver, you will ALSO get
all the subsequent versions during one year absolutely FREE!

IBProvider v3.8.2. Are your data access components ready for Firebird 3?

Are your data access components ready for Firebird 3?

We are continuing to actively add new functionality of Firebird 3 DBMS to IBProvider.

Let us remind you that already 2 months ago we added support of BOOLEAN data type from Firebird 3. In the new version of IBProvider Professional, we added support of PACKAGE instruction.

Now you can put in order a bulk of database procedures and functions and group them by sense into individual modules (PACKAGE). This arrangement will substantially simplify understanding and maintenance of SQL code.

Firebird 3 - PACKAGE instruction

With IBProvider, you can use the following PACKAGE capabilities in your programs:

Execution of DDL queries for creating, modifying and deleting PACKAGE.
Stored procedures call from PACKAGE in the queries "exec SP …", "{call SP …}"

VBScript example

option explicit dim cn set cn=createobject("ADODB.Connection") cn.Provider="LCPI.IBProvider.3" cn.Properties("location")="vxpsp2-fb30:e:\database\ibp_test_fb30_d3.gdb" cn.Properties("user id")="sysdba" cn.Properties("password")="masterkey" cn.Properties("dbclient_library")="fbclient_30.dll" cn.Properties("ctype")="win1251" ' This is RUSSIAN code page! cn.Properties("auto_commit")=true cn.Properties("exec_sp_named_param")=true call cn.Open("") wscript.echo "Provider Version: "&cn.Properties("Provider Version").Value wscript.echo "DBMS Name : "&cn.Properties("DBMS Name").Value wscript.echo "DBMS Version : "&cn.Properties("DBMS Version").Value wscript.echo "" '---------------- dim cmd dim rs set cmd=createobject("ADODB.Command") cmd.ActiveConnection=cn '---------------- wscript.echo "create packages" cmd.CommandText = _ "recreate package test_pack1 as"&vbCrLf& _ "begin"&vbCrLf& _ " procedure proc(in1 integer)"&vbCrLf& _ " returns (out1 integer);"&vbCrLf& _ "end;"&vbCrLf& _ ""&vbCrLf& _ "recreate package body test_pack1 as"&vbCrLf& _ "begin"&vbCrLf& _ " procedure proc(in1 integer)"&vbCrLf& _ " returns (out1 integer)"&vbCrLf& _ " as"&vbCrLf& _ " begin"&vbCrLf& _ " out1=-in1;"&vbCrLf& _ " end;"&vbCrLf& _ "end;"&vbCrLf& _ ""&vbCrLf& _ "recreate package test_pack2 as"&vbCrLf& _ "begin"&vbCrLf& _ " procedure proc(in1_str varchar(64) character set ascii)"&vbCrLf& _ " returns (out1_str varchar(64) character set ascii);"&vbCrLf& _ "end;"&vbCrLf& _ ""&vbCrLf& _ "recreate package body test_pack2 as"&vbCrLf& _ "begin"&vbCrLf& _ " procedure proc(in1_str varchar(64) character set ascii)"&vbCrLf& _ " returns (out1_str varchar(64) character set ascii)"&vbCrLf& _ " as"&vbCrLf& _ " begin"&vbCrLf& _ " out1_str=upper(in1_str);"&vbCrLf& _ " suspend;"&vbCrLf& _ " end;"&vbCrLf& _ "end;"&vbCrLf& _ ""&vbCrLf& _ "recreate procedure proc"&vbCrLf& _ "returns (x integer)"&vbCrLf& _ "as"&vbCrLf& _ "begin"&vbCrLf& _ "x=1234;"&vbCrLf& _ "end;" set rs=cmd.Execute() 'check errors while(not (rs is nothing)) set rs=rs.NextRecordset() wend wscript.echo "" '---------------- wscript.echo "exec test_pack1.proc" cmd.CommandText="exec test_pack1.proc" cmd("in1")=2 call cmd.Execute() wscript.echo "out1: "&cstr(cmd("out1").value) wscript.echo "" '---------------- wscript.echo "exec test_pack2.proc" cmd.CommandText="exec test_pack2.proc" cmd("in1_str")="qwerty" set rs=cmd.Execute() wscript.echo "out1_str: """&rs("out1_str").value&"""" wscript.echo "" set rs=nothing '---------------- wscript.echo "exec proc" cmd.CommandText="exec proc" call cmd.Parameters.Refresh() call cmd.Execute() wscript.echo "x: "&cstr(cmd("x").value) wscript.echo "" '---------------- wscript.echo "OK"

Work results:

The new IBProvider version is faster and more stable

With each new IBProvider release, we increase the number of tests and combinations included into our test system.

In the new release, we fixed an error of the type:

BUG-CHECK at [TIBP_RW_TableStorage_Base::RowDataDpmBlock_Verification] [003]. Possible reason: Wrong DPM block [000000000490:0000] size: 1692. Wait size: 16.

The problem manifests in the rowsets, which entry size exceeds 4K, when changing intensively column values. The error is present in all IBProvider v3 bilds starting from RC5. The repair is available starting from the version 3.8.1.

In the process of IBProvider new functionality implementation, the mandatory stage is preliminary refactoring of the existing code. This time, we managed to reduce the number of service requests to server in the process of preparation of non-standard queries for the execution of stored procedures: "exec SP …", "{call SP …}"

Our short-range plans include transfer of 64bit IBProvider builds to Visual Studio 2010.

Summary

A year ago, we came to the finish line of the third IBProvider version. Then we crossed it and without a one-day stop moved further. Now, we offer you support of the whole line of Firebird and Interbase servers and the functionality we didn't dream about even in our boldest dreams. We thank all who have stayed with us or joined us just recently.

The new IBProvider Professional 3.8.2 is READY TO WORK with Firebird 3

Are your programs ready?

Download it right now!!!

Or purchase a time-unlimited personal license

In addition to the newest driver, you are GUARANTEED to receive
all subsequent versions within one year FOR FREE!

IBProvider v3.8. UDF in metadata schemas. Configuring of transaction isolation parameters. New "Free".

User Defined Functions in metadata schemas.

The provider publishes data about UDF in PROCEDURES and PROCEDURE_PARAMETERS schemas.
The column [PROCEDURES].[PROCEDURE_DEFINITION] contains the text with UDF declarations - "DECLARE EXTERNAL FUNCTION ...".
The provider supports the all FB/IB versions and Yaffil. Including - Firebird 3.0 (ODS 12.0).

Configuring of transaction isolation levels.

Now you can configure the parameters for supported isolation levels: read_committed, repeatable_read и serializable. For these purposes were defined the new initialization properties: ib_tr_params__read_committed, ib_tr_params__repeatable_read, ib_tr_params__serializable.

The provider supports next tags: read, write, wait, nowait, rec_version, no_rec_version, read_committed, concurrency, consistency.

Important changes

Transaction parameters

Isolation	Old parameters	New parameters
Read Committed	write read_committed no_rec_version wait	write read_committed rec_version nowait
Repeatable Read	write concurrency wait	write concurrency nowait
Serializable	write consistency wait	write consistency nowait

The support for isolation level CHAOS was removed.
The support for ISOLATIONLEVEL_UNSPECIFIED was removed.

The support for SQL_BIT in ODBC function CONVERT.

When you work with FB3, IB7+, the statement "{fn CONVERT(value, SQL_BIT)}" will be transformed into "CAST((value) AS BOOLEAN)".

New runtime of Visual Studio 2008.

The new provider uses a new runtime of Visual Studio 2008 - 9.0.30729.5570.

New Free IBProvider v3.8.

All last changes from IBProvider Professional Edition.
Added the support of Firebird 2.1.

IBProvider v3.7. Support for BOOLEAN [Firebird v3].

Append the support for new data type from Firebird v3 - BOOLEAN.

Read/write the simple BOOLEAN-column
Read/write the BOOLEAN-column with array
Support for BOOLEAN in schemas COLUMNS, PROCEDURE_COLUMNS, PROCEDURE_PARAMETERS, PROCEDURES

Configuring of IBProvider for work with FB3 is carried out automatically.

IBProvider v3.6. New interfaces for rowset and new metadata schema.

New interfaces for rowset: IRowsetRefresh, IRowsetResynch

New interfaces are used to reload the values of columns in the rowset.
By default, support of IRowsetRefresh and IRowsetResynch interfaces disabled. For activation of these interfaces, need to assign "true" to the properties IRowsetRefresh, IRowsetResynch.
For configuration of work of these interfaces, defined new properties: refresh_sql, refresh_trans_type, refresh_trans_level.
Note that ADODB.Field.UndelyingValue can't correctly work with IRowsetRefresh interface. Our common recommendations for ADODB users - activate and use the IRowsetResynch interface only.

option explicit '-------------------------------------------------------------------------- dim cn set cn=createobject("ADODB.Connection") cn.Provider="LCPI.IBProvider.3" cn.Properties("location")="localhost:d:\database\employee.fdb" cn.Properties("user id") ="SYSDBA" cn.Properties("password")="masterkey" call cn.Open() call cn.BeginTrans() dim cmd set cmd=createobject("ADODB.Command") cmd.ActiveConnection=cn cmd.Properties("IRowsetResynch")=true 'Robert Nelson cmd.CommandText="select * from employee where EMP_NO=2" dim rs set rs=cmd.execute() wscript.echo "[CurrentValue] FIRST_NAME : "&print_value(rs("first_name").value) wscript.echo "[UnderlyingValue] FIRST_NAME : "&print_value(rs("first_name").UnderlyingValue) wscript.echo "--- [update]" call cn.Execute("update employee set first_name=upper(first_name) where emp_no=2") wscript.echo "[CurrentValue] FIRST_NAME : "&print_value(rs("first_name").value) wscript.echo "[UnderlyingValue] FIRST_NAME : "&print_value(rs("first_name").UnderlyingValue) wscript.echo "--- [resync]" call rs.Resync() wscript.echo "[CurrentValue] FIRST_NAME : "&print_value(rs("first_name").value) wscript.echo "[UnderlyingValue] FIRST_NAME : "&print_value(rs("first_name").UnderlyingValue) call wscript.quit(0) '++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ private function print_value(v) dim s if(IsNull(v))then s=s&"#NULL" else s=s&cstr(v) end if print_value=s end function 'print_value

Output:

New scheme of metadata: DBSCHEMA_IBP_FIELD_DIMENSIONS

A new scheme provides the information about dimension of column or SP parameter with array data type.
Schema identifier: {769A128E-04BF-11D8-AE8B-00A0C907DB93}
Schema columns:
- RELATION_CATALOG [WSTR]
- RELATION_SCHEMA [WSTR]
- RELATION_NAME [WSTR]
- FIELD_NAME [WSTR]
- FIELD_GUID [GUID]
- FIELD_PROPID [UI4]
- DIMENSION [UI4]. Numbering begins at one
- LOWER_BOUND [I4]
- UPPER_BOUND [I4]
Restriction columns: RELATION_CATALOG, RELATION_SCHEMA, RELATION_NAME, FIELD_NAME.
Default sort order: RELATION_CATALOG, RELATION_SCHEMA, RELATION_NAME, FIELD_NAME, DIMENSION.

option explicit '-------------------------------------------------------------------------- private const adSchemaProviderSpecific=-1 private const guid_DBSCHEMA_IBP_FIELD_DIMENSIONS="{769A128E-04BF-11D8-AE8B-00A0C907DB93}" '-------------------------------------------------------------------------- dim cn set cn=createobject("ADODB.Connection") cn.Provider="LCPI.IBProvider.3" cn.Properties("location")="localhost:d:\database\employee.fdb" cn.Properties("user id") ="SYSDBA" cn.Properties("password")="masterkey" call cn.Open() dim restrictions restrictions=Array(empty,empty,"JOB","LANGUAGE_REQ") dim rs set rs=cn.OpenSchema(adSchemaProviderSpecific, _ restrictions, _ guid_DBSCHEMA_IBP_FIELD_DIMENSIONS) dim nRec nRec=0 while not rs.eof nRec=nRec+1 wscript.echo "---------------- ["&nRec&"]" wscript.echo "RELATION_CATALOG: "&print_value(rs("RELATION_CATALOG").value) wscript.echo "RELATION_SCHEMA : "&print_value(rs("RELATION_SCHEMA").value) wscript.echo "RELATION_NAME : "&print_value(rs("RELATION_NAME").value) wscript.echo "FIELD_NAME : "&print_value(rs("FIELD_NAME").value) wscript.echo "FIELD_GUID : "&print_value(rs("FIELD_GUID").value) wscript.echo "FIELD_PROPID : "&print_value(rs("FIELD_PROPID").value) wscript.echo "DIMENSION : "&print_value(rs("DIMENSION").value) wscript.echo "LOWER_BOUND : "&print_value(rs("LOWER_BOUND").value) wscript.echo "UPPER_BOUND : "&print_value(rs("UPPER_BOUND").value) call rs.MoveNext() wend wscript.echo "" wscript.echo "total record count: "&cstr(nRec) call wscript.quit(0) '++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ private function print_value(v) dim s if(IsNull(v))then s=s&"#NULL" else s=s&cstr(v) end if print_value=s end function 'print_value

Output:

IBProvider v3.5. Support for Firebird 2.5.1. Automatic generation of SQL queries has been improved. Support for parameters in SQL scripts.

Support of parameters in SQL scripts

The new IBProvider version supports parameters in the SQL-scripts containing several SQL queries. When this option is used, the following implementation limitations should be taken into account:

Only named parameters are supported.
The user must adjust parameter descriptions by his own.

dim cmd set cmd=createobject("ADODB.Command") cmd.NamedParameters=true cmd.ActiveConnection=cn rem enable interface for the RecordCount support cmd.Properties("IRowsetScroll").value=true cmd.CommandText = _ "select first_name,last_name" & vbCrLf & _ " from employee" & vbCrLf & _ " where emp_no=:emp_no;" & vbCrLf & _ "select p.proj_id,p.proj_name,p.proj_desc" & vbCrLf & _ " from project p join employee_project ep on p.proj_id=ep.proj_id" & vbCrLf & _ " where ep.emp_no=:emp_no;" rem Pete Fisher call cmd.Parameters.Append _ (cmd.CreateParameter("emp_no",adVariant,adParamInput,-1,24)) dim rs set rs=cmd.Execute() rem output: 1 wscript.echo "rs1 size:"&rs.RecordCount set rs=rs.NextRecordset rem output: 2 wscript.echo "rs2 size:"&rs.RecordCount

If a problem occurs, we recommend to study error messages for each script query. IBProvider forms detailed error text descriptions.

Automatic generation of the SQL queries INSERT, DELETE and UPDATE based on the command SELECT

This functionality was implemented to extend the possibilities of working with updatable rowsets and for automatic generation of commands.

In the previous releases, definition of primary key columns and generation of queries for recording changes back to the database were supported only for a trivial query of the type "select * from MY_TABLE". In the new version, this has been dramatically improved. Now the provider extensively supports SQL queries:

With enumeration of columns: "select col1, col2 t_col2, col3 as t_col3, t.col4, t.col5 t_col5, t.col6 as t_col6 from my_table as t". Column name can be put in parentheses.
With selection of all columns of the table: "select t.* from my_table t"
With the section WHERE: "select <columns> from my_table t where <conditions>"
With the sections PLAN, ORDER BY, FOR UPDATE, ROWS

Existing limitations:

The query must return data from only one table.
The list of returned columns of the set can only contain basic columns of the table and must not contain repetitions.
The combining of queries "select t1.* from my_table t1 union select t2.* from my_table t2" is not supported. However, UNION can be used in a subquery of the section WHERE.
Result set must contains all columns of primary key

dim cmd set cmd=createobject("ADODB.Command") cmd.NamedParameters=true cmd.ActiveConnection=cn rem enable interface for the updatable recordset cmd.Properties("IRowsetUpdate").value=true cmd.CommandText = _ "select emp_no,first_name,last_name from employee where emp_no=:x" rem Pete Fisher cmd("x")=24 dim rs set rs=cmd.Execute() wscript.echo "FIRST_NAME :"&rs("first_name").value wscript.echo "LAST_NAME :"&rs("last_name").value rs("first_name").value =ucase(rs("first_name").value) rs("last_name").value =ucase(rs("last_name").value) call rs.UpdateBatch() set rs=nothing rem ---- wscript. echo "-------------------- [re-execute]" set rs=cmd.execute() wscript.echo "FIRST_NAME :"&rs("first_name").value wscript.echo "LAST_NAME :"&rs("last_name").value rem OUTPUT: FIRST_NAME :Pete rem OUTPUT: LAST_NAME :Fisher rem OUTPUT: -------------------- [re-execute] rem OUTPUT: FIRST_NAME :PETE rem OUTPUT: LAST_NAME :FISHER

Introduction of support for Firebird 2.5.1

Now Firebird 2.5.1 is used as the main test server of the provider. In the new IBProvider version its changes are taken into account.

The new IBProvider version allows to write less code for working with database at the expense of batch execution of SQL queries and automatic command generation. In addition, the new IBProvider supports the latest versions of the databases Interbase XE (2010) and Firebird 2.5.1

Do you want to create FAST and compact 32-bit and 64-bit applications
using the CAPABILITIES of the latest Firebird and Interbase versions?

Choose IBProvider Professional ver.3.5

Download it right now!!!

Or purchase the time-unlimited version

In addition to the newest driver, you are GUARANTEED to receive
all subsequent versions within a year absolutely FREE!

4 key distinctions of the new IBProvider v3.4 that make your applications faster

Possibility to abort lengthy loading of resulting rowsets in SQL scripts.
Control and adjustment at your own discretion of deferred data loading.
Background garbage collector became multithreaded.
Accelerated work with BLOB fields and arrays in updatable rowsets.

1. Now you can abort loading of resulting rowsets in sql scripts

The new IBProvider version has a better implementation of command execution cancellation. Now it is possible to abort not only execution of queries but also loading of resulting rowsets from SQL scripts. This allows to cancel a lengthy loading and continue operation of your application.

2. Now you can control deferred data loading

To optimize performance, the data stored in arrays and BLOB fields is not transferred to the client during execution of the main query. Instead, it is loaded on as-needed basis when the client clearly requests the information.

New IBProvider initialization properties allow to change this behavior. Now you can disable deferred loading of BLOB and arrays for columns and OUT parameters. It is controlled by the appropriate properties deferred_data and deferred_out_param.

Particularities of deferred reading with out parameters and transactions

By default, if OUT parameters are used together with automatic transactions, the data is loaded immediately and deferred loading is disabled. This allows to compete the automatic transaction before exiting the ICommand::Execute method (Command.Execute in case of ADODB).

If a command uses OUT parameters, deferred loading is possible only when BLOB data has been received in the form of an object (Storage Object).

If deferred loading is enabled, the object will load data from the database on request and this will require an active transaction.

If deferred loading is disabled, the BLOB object will be first loaded to the local temporary data storage, and the object will return data from this storage. In this case, an active transaction is not required.

What is temporary data storage?

To store the data used within the framework of one connection, IBProvider can create a temporary pagefile. Initially, the data is loaded to short-term memory cache, which size is defined by the new initialization property temp_stg__memory_usage. If new data is too big for cache, the oldest information is uploaded to the file, and the new information is stored in the memory.

3. Background garbage collector is now multithreaded

In the previous releases, the background garbage collector of updatable rowsets was single-threaded. Now it parallelizes its work. Local temporary data storage also uses background garbage collector.

4. Accelerated work with blob fields and arrays in updatable rowsets.

For the first time ever, deferred and asynchronous operations are used to remove BLOB data from local storages. This allows to reduce actual time a thread spends within IBProvider code.

These four key changes,
ensure better performance of your client application that
will continue to perform its main task
while IBProvider is doing all "dirty" work in the background.

Let all "dirty" work be done by IBProvider ver.3.4

Download it right now!!!

Or purchase the time-unlimited version

In addition to the newest driver, you are GUARANTEED to receive
all subsequent versions within a year absolutely FREE!

In the new IBProvider version, we introduced support of the BASE64 charset of InterBase XE, improved algorithms, reduced requirements to memory and corrected errors

The list of changes implemented in IBProvider 3.3.2.11510:

Introduction of support to the BASE64 charset (Interbase 9.0.3, Interbase XE (2010))
Improvement of error processing for setting parameter OUT values
Improvement of parameter OUT values processing. Fail safety in case of critical errors.
Correction of content formation for the column DBSCHEMA_COLUMNS::COLLATION_NAME.
Optimization of the ICommand::Execute method
- Reduction of requirements to memory.
- Improvement of work algorithms.
Disable of multiple definition of IN values for one and the same command parameter
Disable of multiple definition of a new value for the updatable rowset column.

>> Receive the updated IBProvider right now!!!

Attention: In addition to the newest driver, you are GUARANTEED to receive all subsequent versions within a year absolutely FREE!

5 key innovations in Interbase XE (Interbase 2010).

How to create a Firebird or Interbase database by using ADOX and Visual C# .NET (or VBScript).

Usage of BOOLEAN and GUID types in Firebird and Interbase.

Quick start with Borland Interbase SQL Server.

Working with Firebird and Interbase in Delphi.

Working with Firebird and Interbase with limited system rights.

Charsets and collations in Firebird and Interbase.

Firebird Sql Server for beginners.

Interbase and Firebird Developer's manual for ADO .Net. Part 3. Additional features: DDL, metadata schemas, ODBC Escape Sequences

Interbase and Firebird Developer's manual for ADO .Net. Part 2. Using code generators and tools of Visual Studio 2005 - VS 2008

10 reasons to upgrade Interbase and Firebird application to 64 bits.

Interbase and Firebird Developer's manual for Visual Studio. Part 1. Introduction to ADO .Net.

New features of Firebird 2.0. Examples for ADO .Net (c#).

Integration Services. Part 1. Import and data processing in Firebird and Interbase. (MS SQL Server 2005 Business Intelligence).

ODBC or OLE DB? Choosing a driver for InterBase and Firebird..

We have published forum topic with frequently asked questions about MS SQL Server Business Intelligence.

The Compete Guide to ODBC Escape Sequences in Firebird and Interbase has published.

We have published forum topic with frequently asked questions about MS SQL Linked Server technology.

Differences between IBProvider versions article was updated. Existing and new functions has grouped by categories.

New example of the storing image into the BLOB field.

Article Using new features of the Firebird 2.1 in the ADO .Net. was published.

New sample of using Crystal Reports with Firebird in .Net 2 (VS 2005). Download here

26 and 1 samples of using ADO .Net 2.0. with Firebird 2.0. Download here

New article was published: Differences between IBProvider versions

Article How to connect InterBase database to MS SQL server and it VBScript sample was updated. Tips: using manual transaction mamagement