RE: Migration tools/plan from oracle 7.3 to Mysql 4.0
Give a look to SQLyogs ODBC Import Tool. It can be found at http://www.webyog.com Regards, Karam --- [EMAIL PROTECTED] wrote: > > Hi, >I have to migrate oracle 7.3 database to > MySql , for oracle used Pro*C. > In the front end used Java, JNI, RMI and Pro*C. > In the migration process what will be the best > equivalent of Pro*C in MySql. > Ans also need to use XML, for the above environment > what are the best langauge suit for XML handling( > c++ or java) and what will be the best parsers for > XML (like jaxp ..etc). Please advise me here. > > Thanks, > Narasimha > 91 98456 82459 > > -Original Message- > From: Lakshmi NarasimhaRao (WT01 - TELECOM SERVICE > PROVIDER) > Sent: Tue 8/17/2004 3:08 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: > Subject: RE: Migration tools/plan from oracle 7.3 > to Mysql 4.0 > > > > > 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. > > > > > > > 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. > ___ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Migration tools/plan from oracle 7.3 to Mysql 4.0
Hi, I have to migrate oracle 7.3 database to MySql , for oracle used Pro*C. In the front end used Java, JNI, RMI and Pro*C. In the migration process what will be the best equivalent of Pro*C in MySql. Ans also need to use XML, for the above environment what are the best langauge suit for XML handling( c++ or java) and what will be the best parsers for XML (like jaxp ..etc). Please advise me here. Thanks, Narasimha 91 98456 82459 -Original Message- From: Lakshmi NarasimhaRao (WT01 - TELECOM SERVICE PROVIDER) Sent: Tue 8/17/2004 3:08 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: Subject: RE: Migration tools/plan from oracle 7.3 to Mysql 4.0 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. 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.
Re: Migration tools/plan from oracle 7.3 to Mysql 4.0
Martijn Tonies wrote: Re: Migration tools/plan from oracle 7.3 to Mysql 4.0With "application code", I meant that you: - have to change your queries so that they include the full VIEW sql, because MySQL doesn't have an alternative - have to recreate your stored procedures in application code and do you work at the client or a middle tier MySQL 5 has stored procedures. Of course, it's still alpha. - have to recreate all your triggers in application code to do additional work instead of the triggers on the database - have to bring your checks into the application (but they won't be safe anyway, 'cause MySQL Classic doesn't have transactions) Well, if you need transactions, then why not use MySQL 4 Standard (or Pro) which does support InnoDB tables and transactions? With regards, Martijn Tonies Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Migration tools/plan from oracle 7.3 to Mysql 4.0
Re: Migration tools/plan from oracle 7.3 to Mysql 4.0Hi Narasimha, Please reply to the MySQL list instead of me personally only. > How we can write the equivalent code for triggers of >oracle in Mysql?. Shall we do it by using User Defined >Functions?. Can we use database queries inside the user >defined functions?. Please advise. As far as I can see, User Defined Functions have nothing to do with it. If you need Stored Procedures, Triggers and working constraints, MySQL is not the right database engine for you. Plain and simple. The equivalent of triggers in application code highly depends on the type of trigger. For example, if you trigger does a couple of additional INSERTs, you need to copy this code to your application. It ain't easy. And when it comes to constraints, it's downright "hairy". I wouldn't trust my data to a database without constraints. 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]
Re: Migration tools/plan from oracle 7.3 to Mysql 4.0
Re: Migration tools/plan from oracle 7.3 to Mysql 4.0With "application code", I meant
that you:
- have to change your queries so that they include the full VIEW sql, because MySQL
doesn't have an alternative
- have to recreate your stored procedures in application code and do you work at the
client or a middle tier
- have to recreate all your triggers in application code to do additional work instead
of the triggers on the database
- have to bring your checks into the application (but they won't be safe anyway,
'cause MySQL Classic doesn't have transactions)
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL Server.
Upscene Productions
http://www.upscene.com
I had the application code. What will be the eqaulant of views in Mysql?. I
mean in what way i have to migrate the views, triggers, stored procedures and
contraints of Oracle to Mysql 4.0 classic version (This does not vave innodb engine).
Thanks,
Narasimha
919845682459
-Original Message-
From: Martijn Tonies [mailto:[EMAIL PROTECTED]
Sent: Tue 8/17/2004 3:45 PM
To: Lakshmi NarasimhaRao (WT01 - TELECOM SERVICE PROVIDER); [EMAIL PROTECTED]
Cc:
Subject: Re: Migration tools/plan from oracle 7.3 to Mysql 4.0
> 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.
>
Well, what other alternative do you have but application code?
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
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.
Re: Migration tools/plan from oracle 7.3 to Mysql 4.0
> 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. > Well, what other alternative do you have but application code? 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]
RE: Migration tools/plan from oracle 7.3 to Mysql 4.0
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.
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]
