I am trying to import tables from a Firebird 2.1 database to SQL Server 2008 R2 for the purpose of utilizing SSRS to build reports. I have tried several drivers, most recently, the LCPI OLE DB Provider for InterBase [v3] from IBProvider.com. I can successfully make a connection to the table as well as preview the table data, however after selecting the tables I wish to import and moving to the next step, I consistently receive the following error: No information about database object charset. (LCPI.IBProvider.3) ------------------------------ Program Location: at System.Data.OleDb.OleDbConnectionInternal.ProcessResults(OleDbHResult hr) at System.Data.OleDb.OleDbConnectionInternal.GetSchemaRowset(Guid schema, Object[] restrictions) at System.Data.OleDb.OleDbConnection.GetOleDbSchemaTable(Guid schema, Object[] restrictions) at Microsoft.DataTransformationServices.Controls.ProviderInfos.MetadataLoader.LoadColumnsFromTable(IDbConnection myConnection, String[] strRestrictions) at Microsoft.SqlServer.Dts.DtsWizard.OLEDBHelpers.LoadColumnsFromTable(MetadataLoader metadataLoader, IDbConnection myConnection, String[] strRestrictions, DataSourceInfo dsi) at Microsoft.SqlServer.Dts.DtsWizard.TransformInfo.PopulateDbSourceColumnInfoFromDB(IDbConnection mySourceConnection) at Microsoft.SqlServer.Dts.DtsWizard.TransformInfo.PopulateDbSourceColumnInfo(IDbConnection mySourceConnection, ColumnInfoCollection& sourceColInfos) It is important to note that the settings i am using for the CHARACTER SET are ISO8859_1 as directed by the DB Creator. I can successfully connect to the DB and pull data using MS Access 2010 and the FireBird ODBC driver from my desktop, however, on Win Server 2008 from the SQL Server Import Data tool, I cannot.

OK...with the help of another support forum, I am past this error and on to the next one. appending to connection string the "schema_cache=0" will disable reading the information about all columns in database. Past that, FB has a column type of 130 that needed to be mapped to a SQL Server column type of TEXT.

One other item of note...after extensive work trying many different approaches (drivers, etc) pulling data from FireBird to SQLServer on Win Server 2008, the drivers from IBProvider proved to be the best solution. The freely available FireBird drivers worked much of the time, however, we had flaky results pulling the data at times which was unacceptable.