problem porting MySQL to SQLServer

Hi I am trying to port a MySQL database to microsoft SQL server 2000. I
downloaded the mysql odbc driver, both versions 3.1 and 5.0. I am able to
create the odbc machine source and the connection to the MySQLmachine works
(using access)
but when I try to import a table into Access I get the error Microsoft access
reserved error (-7701) there is no message for this error.
Anyhow just wondering if anyone has any ideas? I am hoping that the MySQL
tables are not too large.
thanks.
--
Paul G
Software engineer.Hello Paul,
> Hi I am trying to port a MySQL database to microsoft SQL server 2000. I
> downloaded the mysql odbc driver, both versions 3.1 and 5.0. I am able to
> create the odbc machine source and the connection to the MySQLmachine
works
> (using access)
> but when I try to import a table into Access I get the error Microsoft
access
> reserved error (-7701) there is no message for this error.
> Anyhow just wondering if anyone has any ideas? I am hoping that the MySQL
> tables are not too large.
You might try our database tool: Database Workbench ( www.upscene.com )
It includes a Schema Migration and DataPump tool.
Connections to both MySQL and MS SQL Server natively.
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com|||Hi thanks for the response. Just wondering if you have a demo, if it works
ok I can most likely get management to make a purchase if the price is not
too high.
thanks.
--
Paul G
Software engineer.
"Martijn Tonies" wrote:
> Hello Paul,
> > Hi I am trying to port a MySQL database to microsoft SQL server 2000. I
> > downloaded the mysql odbc driver, both versions 3.1 and 5.0. I am able to
> > create the odbc machine source and the connection to the MySQLmachine
> works
> > (using access)
> > but when I try to import a table into Access I get the error Microsoft
> access
> > reserved error (-7701) there is no message for this error.
> > Anyhow just wondering if anyone has any ideas? I am hoping that the MySQL
> > tables are not too large.
> You might try our database tool: Database Workbench ( www.upscene.com )
> It includes a Schema Migration and DataPump tool.
> Connections to both MySQL and MS SQL Server natively.
>
> --
> With regards,
> Martijn Tonies
> Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
> Server
> Upscene Productions
> http://www.upscene.com
> Database development questions? Check the forum!
> http://www.databasedevelopmentforum.com
>
>|||fixed the problem, seemed to work on another machine with more memory so most
likely memory related.
--
Paul G
Software engineer.
"Paul" wrote:
> Hi thanks for the response. Just wondering if you have a demo, if it works
> ok I can most likely get management to make a purchase if the price is not
> too high.
> thanks.
> --
> Paul G
> Software engineer.
>
> "Martijn Tonies" wrote:
> > Hello Paul,
> >
> > > Hi I am trying to port a MySQL database to microsoft SQL server 2000. I
> > > downloaded the mysql odbc driver, both versions 3.1 and 5.0. I am able to
> > > create the odbc machine source and the connection to the MySQLmachine
> > works
> > > (using access)
> > > but when I try to import a table into Access I get the error Microsoft
> > access
> > > reserved error (-7701) there is no message for this error.
> > > Anyhow just wondering if anyone has any ideas? I am hoping that the MySQL
> > > tables are not too large.
> >
> > You might try our database tool: Database Workbench ( www.upscene.com )
> > It includes a Schema Migration and DataPump tool.
> >
> > Connections to both MySQL and MS SQL Server natively.
> >
> >
> > --
> > With regards,
> >
> > Martijn Tonies
> > Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
> > Server
> > Upscene Productions
> > http://www.upscene.com
> > Database development questions? Check the forum!
> > http://www.databasedevelopmentforum.com
> >
> >
> >|||On Mon, 12 Sep 2005 11:12:04 -0700, "Paul"
<Paul@.discussions.microsoft.com> wrote:
>fixed the problem, seemed to work on another machine with more memory so most
>likely memory related.
If all else fails, export the data into flat files and BCP them into
SQLServer. Not a bad strategy in any case.
J.|||Thanks for the information, just wondering how to export the data into flat
files, can you do this using MySQLFront?
--
Paul G
Software engineer.
"jxstern" wrote:
> On Mon, 12 Sep 2005 11:12:04 -0700, "Paul"
> <Paul@.discussions.microsoft.com> wrote:
> >fixed the problem, seemed to work on another machine with more memory so most
> >likely memory related.
> If all else fails, export the data into flat files and BCP them into
> SQLServer. Not a bad strategy in any case.
> J.
>|||On Mon, 12 Sep 2005 12:15:04 -0700, "Paul"
<Paul@.discussions.microsoft.com> wrote:
>Thanks for the information, just wondering how to export the data into flat
>files, can you do this using MySQLFront?
Or CSV.
Sorry, I'm rather rusty on MySQL, but I'm sure it's doable.
J.|||> Thanks for the information, just wondering how to export the data into
flat
> files, can you do this using MySQLFront?
And with our tool as well ;-)
That is, IF it's version MySQL 4 and up.
You might want to try the DataPump tool in it -- that should not have
problems with MySQL < 4... Haven't tried it though.
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com