Import from Interbase

Hi all...

How do I import data from a Borland Interbase 6 database to a SQL Server 2005 Standard database?

When I try do an import from within Management Studio, I can connect to the ODBC datasource, but I have to write a manual query for each individual table to get the data across. I am using the OpenSource Firebird ODBC driver.

The funny thing here, is that I tried to import into a SQL Server 2000 database and it worked 100%. I could connect to the interbase DB, all tables were pulled, I ticked each on and completed the import wizard. It worked 100%. SQL Server 2005 will not work though. And using exactly the same methods and properties as I did when I tried with 2000.

In case you were wondering, I do have the entire schema created correctly on the SQL Server side. It is just the data I need to import.

Any ideas?

I'm not sure why SQL 2005 is different from SQL 2000, but I can offer a simple solution. If you can import everything just fine to SQL 2000, then once that's complete, take a database backup and then restore it to SQL 2005.|||

I hear you Greg and concur... Only problem being that that is fine on my dev system where I have both SQL versions installed.

When, however, it comes time to upgrade my clients server, we are going in in the evening when there are no staff there, and have to perform the upgrade then. I don't want to have to install SQL 2000, do the import, do a backup, then uninstall it and install SQL 2005. Seems like a *** work around to me. I just want to know how to get SQL 2005 to work the same as SQL 2000 does on imports.

Any more ideas?

|||

Hello Michael -

A fallback method I use when I have two disparate databases is to export from the source DB out to text and then bring it into SQL. There are some disadvantages with this method, since you need more space, it takes longer to do, and you lose data types on dates and numerics.

When you run the import job from 2K5, are you selecting the same ODBC driver? Have you tried making a DSN with that and doing it that way? How about a distributed query with a SELECT INTO?

Buck

sql