SYBASE to DB2 ....
Raquel
Have also cross posted this to the Mainframe DB2 community.
We have been asked to look into the feasibility and the method of
migrating a SYBASE application to DB2. It is also being debated
whether the application
should be converted to UDB for LUW or DB2 for OS/390. We are looking
at IBM's MTK (Migration toolkit) for conversion. Had some specific
questions regarding
this:
1. Does this toolkit support migration to DB2 for OS/390 (V7.1) or
does it only support migration to UDB for LUW. If IBM MTK does not
support migration to DB2 for OS/390, is there any alternate tool
available which can do the same.
2. Is there anyone who has actually performed SYBASE to DB2 for OS/390
conversion and would they be so kind to share their experiences;
especially vis a vis the amount of manual effort required for
converting the database objects (the SYBASE database being converted
has triggers and stored procedures coded in Transact-SQL, I believe,
which could be a problem
area). Any ballpark estimates on the actual effort required. In SYBASE
database here, there are around 150 Stored procedures and around 120
triggers.
3. Is it 'easier' (in terms of effort required) to migrate to DB2 for
OS/390 or to UDB for LUW. In either cases, what are the pros of one
over the other.
Any other experience which could be useful to us in this regard.
Thank you so much.
Raquel.
Larry
The DB2 migrations page is at
http://www.software.ibm.com/data/db2/migration .
There are ways of getting in touch with the Migration Team and asking
questions off that page. For example, at
http://www-306.ibm.com/software/data/db2/migration/mtk/
are newsgroups where you can post questions. In addition, at
http://www-306.ibm.com/software/data/db2/migration/dbmigteam.html
are contacts for the migration teams.
Larry Edelstein
Serge Rielau
> 1. Does this toolkit support migration to DB2 for OS/390 (V7.1) or
> does it only support migration to UDB for LUW. If IBM MTK does not
> support migration to DB2 for OS/390, is there any alternate tool
> available which can do the same.
I think teh statement is that MTK is helpful for Sybase-> DB2 OS/390
conversion. But this target is not typical. You will likely face more
hands-on rework.
> 2. Is there anyone who has actually performed SYBASE to DB2 for OS/390
> conversion and would they be so kind to share their experiences;
> especially vis a vis the amount of manual effort required for
> converting the database objects (the SYBASE database being converted
> has triggers and stored procedures coded in Transact-SQL, I believe,
> which could be a problem
> area). Any ballpark estimates on the actual effort required. In SYBASE
> database here, there are around 150 Stored procedures and around 120
> triggers.
150 Procedures is (next to) nothing. The triggers are another matter.
How big are those triggers? Do they do error-handling?
DB2 Stinger supports CALL in Trigger...
Sybase triggers are all statement level and no before triggers are
available (unless that has changed without me knowing it).
It pays to convert such triggers into the appropriate form when moving
to DB2 (for each row/for each statement, before/after).
But that requires manual work. MTK will be of limited help there.
Interestingly DB2 zOS provides a trigger support that is closer to
Sybase's model.
So I'd give DB2 zOS the edge on that one.
> 3. Is it 'easier' (in terms of effort required) to migrate to DB2 for
> OS/390 or to UDB for LUW. In either cases, what are the pros of one
> over the other.
DB2 for LUW is the preferred target w.r.t. tooling provided.
Also I believe it is the most common target.
One reason against zOS ia that teh Sybase folks likely come with
Windows/unix skills. Keeping the hardware stable takes one variable out
of the equation. Of course if your company has zOS-skills then the
reverse can be true (drawing on your DB2 zOS skill-set)
Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab