This is one of those "It depends..." situations:
If you have reserved word clashes this will impact the applications.
Certain other T-SQL features have changed behaviour along the way, if these
were used you will
If you're pb code calls views and sprocs your impact should be easier to
deal with due to the abstraction these provide.
If you do not upgrade the open client/odbc connectivity on the client you
will not be able to use new features of 12.5.x, which may not be supported
by PB 6.5 anyway - check the connectivity interoperability map/chart at
sybase.com - based on this there may be no necessity to upgrade.
You will also need to test extensively no matter how much preparation and
research is done. I would recommend that you absorb the release notes for
fixes and changes to behaviour for ASE and OpenClient/ODBC for major
releases since your version... no small task!
<Lily Maria> wrote in message news:firstname.lastname@example.org...
> Thanks for the info.
> I would like to know if there's any online documentation on
> migration and upgrade plan of the ASE 11.5.1 to ASE 12.5.1?
> Do applications created by PB6.5 accessing ASE 11.5.1 data
> require upgrade as well?
> > ASE 12.9? Currently, no released versions of ASE are
> > certified on Win 2003. ASE 12.5.1 will be certified when
> > it is released later this year.
> > Mark Kusma
> > <Lily Maria> wrote in message
> > > news:email@example.com... Need help to
> > > find Sybase's upgrade and migration docs on above
> > > subject? Thank you.