I've posted this question on a few InterBase/Firebird newsgroups but with no
response.
About 7 years ago, I created an InterBase application for a client using
InterBase 4.x. I haven't worked with InterBase since. They now want to
convert this to SQL Server. Actually, all we want to do is to convert the
tables and the data in the tables to SQL Server 2000. The other schema
objects won't get converted. I downloaded the latest version of InterBase
from Borland (V6.x or V7.0, don't recall which). When I attempted to open
the InterBase database, I get an error saying the on-disk structure is
unsupported. Could anyone offer a suggestion on what I can do?
Thanks very much.
Hi
Looks like they changed the format between these versions! If you don't have
a working system, then I guess that you may have to resort to somewhere like
ebay to get one! If you do have a working system, then you might be able to
connect from SQL Server via ODBC and use DTS to get the tables/data.
John
"Amos Soma" <amos_j_soma@.y_a_hoo.com> wrote in message
news:HYudnYvUxYfBgUXd4p2dnA@.buckeye-express.com...
> I've posted this question on a few InterBase/Firebird newsgroups but with
no
> response.
> About 7 years ago, I created an InterBase application for a client using
> InterBase 4.x. I haven't worked with InterBase since. They now want to
> convert this to SQL Server. Actually, all we want to do is to convert the
> tables and the data in the tables to SQL Server 2000. The other schema
> objects won't get converted. I downloaded the latest version of InterBase
> from Borland (V6.x or V7.0, don't recall which). When I attempted to open
> the InterBase database, I get an error saying the on-disk structure is
> unsupported. Could anyone offer a suggestion on what I can do?
> Thanks very much.
>
|||Amos,
I have had to do exactly this for a client. It's not too hard, but it is a
bit fiddly.
The on-disk formats are different, for 4.x and 7.x, so you can't just open
the files. What you have to do is to backup the Interbase 4.x database using
the utility in the 4.x installation, then restore it using the same utility
in the 7.x installation. The backed up file contains all the metadata so 7.x
can re-create it. The utility is called something like gbak, and all the
details are in the Interbase documentation.
Once you've got the data into Interbase you need a 3rd party ODBC driver to
get the data out. I used one of the free ones, forget which. I had to
REMOVE all the triggers from the tables before I could connect with the ODBC
driver though, whch was a pain as there were a lot of them. I eventually
figured out how to automate it, but it is OK to do manually.
If you want to contact me directly take the 'nospam' out of my e-mail
address.
Regards,
Richard
"Amos Soma" <amos_j_soma@.y_a_hoo.com> wrote in message
news:HYudnYvUxYfBgUXd4p2dnA@.buckeye-express.com...
> I've posted this question on a few InterBase/Firebird newsgroups but with
no
> response.
> About 7 years ago, I created an InterBase application for a client using
> InterBase 4.x. I haven't worked with InterBase since. They now want to
> convert this to SQL Server. Actually, all we want to do is to convert the
> tables and the data in the tables to SQL Server 2000. The other schema
> objects won't get converted. I downloaded the latest version of InterBase
> from Borland (V6.x or V7.0, don't recall which). When I attempted to open
> the InterBase database, I get an error saying the on-disk structure is
> unsupported. Could anyone offer a suggestion on what I can do?
> Thanks very much.
>
Monday, March 19, 2012
Interbase to SQL Server 2000 Question
Labels:
application,
created,
database,
firebird,
interbase,
ive,
microsoft,
mysql,
newsgroups,
noresponse,
oracle,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment