Hello,

Currently we have a program developed by a third party enterprise and
the program uses a Linux server Red Hat 5 and Sybase ASA 7.2 and ODBC
driver.

We want to migrate the database from the Sybase ASA 7 to the SQL
Anywhere 11 without touching the program, just the server.

Is there a way to make it? Also, the program will connect to the SQL
Anywhere using the ODBC? I ask this because the programer say that the
program was made to work on the Sybase ASA or ASE and i don't know if
the database server is the same.

Thanks in advance and if you need more details please ask.

Tekorei

On Nov 17, 11:18*pm, RoninTekorei <roninteko... (AT) gmail (DOT) com> wrote:
We did migrate from ASA7 to SA10.
First, you have to upgrade database file from ASA7 to SA10, not only
replace ASA7 with SA10 on Linux. Upgrading (rebuilding) is extremely
fast, about 10 times faster ASA7 to SA10 than ASA7 to ASA7.

Second, i suggest you to replace ASA7 on every client. One of our
clients use Win98 OS (dot matrix printing ), and SA10 doesn't work
on Win98. We have to leave ASA7 ODBC on Win98 PC. At first moments
everything was OK. I don't why (microsoft, borland BDE, sybase ODBC)
there is problem with translation character code page. User input some
852 code page characters, in database file are something else. Same
app in ASA7 to ASA7 combination works fine. Same app in SA10 to SA10
combination works fine. Same app with ASA7 ODBC to SA10 server don't
work. My first target for this is Microsoft, not sybase .

Third, there are many changes from ASA7 to SA10. Some sql script we
have to rewrite for SA10. Very small part of sql scripts, about 5 of
10000, and changes were in correcting group and subselect. Performance
goal after migrating is fantastic. Some very complex procedure with 2
million transaction (insert, update, triggers....) works 10 times
faster on SA10.

Finally, i don't think that you could just replace server. BUT try,
performance of SA10 is great.

Bofcilo wrote:
A possible solution would be to use ASA 9 on the Win98 client. AFAIK,
there were some changes to charset translation between ASA 7 and 9, and
that could help here.

Just my 2 cents

Volker

While there are no actual guarantees you won't run into some
things that will need to be addressed, this kind of backward
compatability should be possible.

There are a few factors to be aware of here:

ODBC drivers and driver manager concerns: You should be
fine here, even if you choose to install the version 11
ODBC driver. The area of ODBC standards and API
backward compatability has received a lot of attention
making the API and swapping ODBC drivers a fairly
safe and transparent thing to do. That is not to say there
may be a few gremlins awaiting you here but those should
be easily identified. Staying with the older ODBC driver
should work unless you hit problems in some other area
(as in, on of the following points below). The good news
here may be you should be good with either the older or
the newer ODBC driver (offering you options).

Database wire protocol: While there should be backward
compatability here, you won't have support for newer
features of that protocol and may not have the benefit of
some bug fixes in this area. Further if you hit an issue due
to a problem in this area you will likely not have any fixes
for your older libraries on the client side and may find a
need to upgrade the client side in that event.

SQL language and feature evolution: Not all problems can be
hidden under backward compatability. The SQL language
itself has evolved and so it may be possible that you find your
older application was using illegal SQL that used to be
tolerated by the older server product but throws an error now.
In these cases you will likely need to look at the application
code.

Deprecated and discontinued features, and coding to bugs:
As SQL evolves so too do product features. You may
find your older application may require features or
functionality that is no longer supported, throws a deprecation
warning or has changed in a way that offends the older
application logic. These kinds of issues need to be addressed
on a case by case basis.


You may find things go without any obvious issues and this just seems
to work. But it is possible will hit 1 or 2 things that will need some
attention. If you do find you hit something do no hesitate to post a new
thread hear and/or contact technical support for assistance.




"RoninTekorei" <ronintekorei (AT) gmail (DOT) com> wrote