Sybase to UDB

[Raquel]

We have a client who wants to convert their Sybase application (with
Stored Procedures, Triggers etc.) to UDB on AIX. Has someone on the
list attempted this? Could they share their experiences (especially
bad experiences) including application and data porting, best third
party tools that could help, specific competencies of personnel
involved etc.

TIA
Raquel.

[Mark A]

"Raquel" <ra****************@yahoo.com> wrote in message
news:9a**************************@posting.google.c om...

We have a client who wants to convert their Sybase application (with
Stored Procedures, Triggers etc.) to UDB on AIX. Has someone on the
list attempted this? Could they share their experiences (especially
bad experiences) including application and data porting, best third
party tools that could help, specific competencies of personnel
involved etc.

TIA
Raquel.

Check the IBM web site to see if they have porting guides.

[Larry]

http://www.software.ibm.com/data/db2/migration

Larry Edelstein

Raquel wrote:

We have a client who wants to convert their Sybase application (with
Stored Procedures, Triggers etc.) to UDB on AIX. Has someone on the
list attempted this? Could they share their experiences (especially
bad experiences) including application and data porting, best third
party tools that could help, specific competencies of personnel
involved etc.

TIA
Raquel.

[Serge Rielau]

Raquel,

First the disclaimer: I'm deep blue

There is a fair bit of experience around with the Migration Toolkit
which you can download from the website Larry pointed you to.

In my experience the biggest problem lies in the expectations.
The standard request is to migrate the app as is, doing minimal changes
to the SQL and procedural logic.
And of course the reason for the migration is that it is supposed to be
faster and scale better on DB2 than on Sybase.

These two requirements do not work together!

If the requirement to DB2 is to emulate Sybase you will see
_significant_ performance degradation because that's what emulation
means. It means trying to be something one is not. And DB2 is not Sybase.

The moment it is acknowledged that the app can be separated into areas
that are performance critical and those that are not, you can rely on
the MTK to migrate the non-critical part and do a reasonably well job.
So all you need to do is deal with the hic-ups.

For the performance critical part you start with the MTK, get yourself
some good DB2 people and redesign the pieces that are not up to snuff.
The reason is that Sybase T-SQL is quite fast (tuned for over a decade),
but the SQL is quite simple, so procedures tend to read a lot like
Visual Basic.
DB2 does not yet have the same level of tuning in SQL PL, but possibly
the best SQL Compiler (did I say I'm biased?).
So you will find yourself replacing procedural logic with SQL to get
onto DB2's strong side. And for that you need someone who thinks in DB2
and not Sybase T-SQL.

Beyond the MTK you need the Development Center (for debugging) which is
shipped with DB2.
I (not IBM) hope to push out an SQL Procedure Tracing facility for
Stinger and an SQL Procedure Profiler for Stinger. They will show up on
developerWorks for DB2. Both will help tune and debug migrated procedures.

You want to start of with Stinger anyway because of the SQL Procedure
enhancements.

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

[Rhino]

"Serge Rielau" <sr*****@ca.eye-be-em.com> wrote in message
news:c8**********@hanover.torolab.ibm.com...

Raquel,
[snip]
I (not IBM) hope to push out an SQL Procedure Tracing facility for
Stinger and an SQL Procedure Profiler for Stinger. They will show up on
developerWorks for DB2. Both will help tune and debug migrated procedures.

You want to start of with Stinger anyway because of the SQL Procedure
enhancements.

What is "Stinger"?

Rhino

[Garfield Lewis]

As is the trend these days, "Stinger" is the code name for the next DB2
release. When it is actually announced it will be given a numerical
designation (unfortunately 7 of 9 is already taken :->).

--
Garfield A. Lewis
DB2 UDB Development,
IBM Canada Laboratory
"Rhino" <rh****@NOSPAM.sympatico.ca> wrote in message
news:pP*********************@news20.bellglobal.com ...

"Serge Rielau" <sr*****@ca.eye-be-em.com> wrote in message
news:c8**********@hanover.torolab.ibm.com...

Raquel,

[snip]

I (not IBM) hope to push out an SQL Procedure Tracing facility for
Stinger and an SQL Procedure Profiler for Stinger. They will show up on
developerWorks for DB2. Both will help tune and debug migrated procedures.
You want to start of with Stinger anyway because of the SQL Procedure
enhancements.

What is "Stinger"?

Rhino

[Mark A]

"Rhino" <rh****@NOSPAM.sympatico.ca> wrote in message
news:pP*********************@news20.bellglobal.com ...

"Serge Rielau" <sr*****@ca.eye-be-em.com> wrote in message
news:c8**********@hanover.torolab.ibm.com...

Raquel,

[snip]

I (not IBM) hope to push out an SQL Procedure Tracing facility for
Stinger and an SQL Procedure Profiler for Stinger. They will show up on
developerWorks for DB2. Both will help tune and debug migrated procedures.
You want to start of with Stinger anyway because of the SQL Procedure
enhancements.

What is "Stinger"?

Rhino

Next release of DB2 which will be either 8.2 or 9.1 (TBD).

[Raquel]

Thank you very much Serge and all the others who replied. Truely
appreciate your inputes.

Regards,
Raquel.