Hi,
Thank you for your response. Could any one give more clarification on the
alternatives for Views, Stored procedures, triggers and contraints of oracle in Mysql
4.0 classic, as MySql 4.0 classic wonot support the InnoDB storage engine.
Thanks,
Narasimha
-----Original Message-----
From: Martijn Tonies [mailto:[EMAIL PROTECTED]
Sent: Tue 8/17/2004 12:59 PM
To: Lakshmi NarasimhaRao (WT01 - TELECOM SERVICE PROVIDER); [EMAIL PROTECTED]
Cc:
Subject: Re: Migration tools/plan from oracle 7.3 to Mysql 4.0
First: please don't hijack threads... And don't quote them completely
if you do.
> I am new to MySql. Could you please let me know the different
migration tools avialable for the migration of oracle 7.3 database to mysql
4.0 classic version.
You could try the Schema Migrator tool in Database Workbench
( www.upscene.com ) - it supports ADO and ODBC connectivity
to MySQL. Might not be perfect, but sure gives you a good start.
>Out of those which one is the best in performance and cost wise. As per my
knowledge views, stored procedures and triggers are not supported in MySql
4.0. Is it correct?.
That is correct. Add to that: no CHECK constraints either.
Foreign Key Constraints and transactions are only supported with
the InnoDB storage engine - read about that in the documentation.
If so, what are all the alternatives for converting the views, stored
procedures and triggers in oracle 7.3 to MySql 4.0. I will be very happy for
giving me a very good explanation on this.
>
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
Confidentiality Notice
The information contained in this electronic message and any attachments to this
message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged
information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL
PROTECTED] immediately
and destroy all copies of this message and any attachments.
