Subject | FW: [IB-Priorities] Migration from M$-Sql |
---|---|
Author | Claudio Valderrama C. |
Post date | 2000-06-21T05:47Z |
I wanted to log this mail for reference here.
C.
-----Original Message-----
From: Tim Uckun [mailto:tim@...]
Sent: Sábado 17 de Junio de 2000 23:53
To: IB-Priorities@egroups.com
Subject: Re: [IB-Priorities] Migration from M$-Sql
very valuable to me as well as the millions of access users in the world. I
have valuated many databases as a possible migration target from access and
I have found three major obstacles.
1) lack of decent and free ODBC/ADO drivers.
2) seemingly archaic limitations on object names (both length and allowable
characters). Most databases seem to think that 30 or characters ought to be
plenty for object names.
3) case sensitivity in queries. Both Access and MS-SQL process all queries
in a case insensitive matter.
Of course there are a thousand minor issues to be dealth with but unless
you have the big 3 fixed it will be very very hard to migrate from an
access database to interbase.
----------------------------------------------
Tim Uckun
Mobile Intelligence Unit.
----------------------------------------------
"There are some who call me TIM?"
----------------------------------------------
------------------------------------------------------------------------
TRAVEL FOR PENNIES ON THE DOLLAR! Get dozens of the best travel agents
competing for your business with our new FREE service.
http://click.egroups.com/1/5571/2/_/_/_/961302447/
------------------------------------------------------------------------
To unsubscribe from this group, send an email to:
IB-Priorities-unsubscribe@egroups.com
C.
-----Original Message-----
From: Tim Uckun [mailto:tim@...]
Sent: Sábado 17 de Junio de 2000 23:53
To: IB-Priorities@egroups.com
Subject: Re: [IB-Priorities] Migration from M$-Sql
>Any document or tool regarding migration from ms-sql or ms-access would be
>Claudio,
>If nothing comes forth, I could help you. I ran with my employer's MSSQL
>database "replicated" on my home machine in InterBase, for a year, using
>the same Delphi client code. There are a few "gotchas" but it is
>definitely doable. If we document what we do, we'll have something of a
>resource available.
very valuable to me as well as the millions of access users in the world. I
have valuated many databases as a possible migration target from access and
I have found three major obstacles.
1) lack of decent and free ODBC/ADO drivers.
2) seemingly archaic limitations on object names (both length and allowable
characters). Most databases seem to think that 30 or characters ought to be
plenty for object names.
3) case sensitivity in queries. Both Access and MS-SQL process all queries
in a case insensitive matter.
Of course there are a thousand minor issues to be dealth with but unless
you have the big 3 fixed it will be very very hard to migrate from an
access database to interbase.
----------------------------------------------
Tim Uckun
Mobile Intelligence Unit.
----------------------------------------------
"There are some who call me TIM?"
----------------------------------------------
------------------------------------------------------------------------
TRAVEL FOR PENNIES ON THE DOLLAR! Get dozens of the best travel agents
competing for your business with our new FREE service.
http://click.egroups.com/1/5571/2/_/_/_/961302447/
------------------------------------------------------------------------
To unsubscribe from this group, send an email to:
IB-Priorities-unsubscribe@egroups.com