Switch to standard view 
  Sybase logo

Q & A

The following are frequently-asked questions about Sybase Adaptive Server Enterprise for 64-bit platforms. If you are running ASE on Solaris, see the Warning for Solaris at the end of this document.

Q: What is 64-bit Adaptive Server Enterprise?

A: 64-bit ASE is a new product, deploying a new technology. It is intended to meet the needs of organizations whose applications are limited by the constraints of 32-bit addressing and want to take advantage of 64-bit addressing, which has recently been provided by operating system vendors.

Q: How is 64-bit ASE different from the ASE I currently use?

A: 64-bit ASE takes advantage of the development of 64-bit addressing in recent versions of several operating systems such as Sun Solaris, HP-UX and AIX. While the SQL syntax is the same, much of the internal code and data structures have changed to support 64-bit addressing. Further, it is linked with different operating system libraries (and thus employs different system calls) from the standard or 32-bit version of ASE.

Q: Should I be using 64-bit ASE?

A: Only if you need 64-bit addressing, which allows larger memory caches. If 32-bit addressing does not meet your current or expected memory requirements, you should consider migrating to 64-bit ASE. If your needs are being met by 32-bit addressing, there is no need to consider 64-bit ASE at this time.

Q: Is 64-bit ASE faster than 32- bit?

A: That depends on your system and the type of processing you do. 64-bit processing consumes more overhead, which can cause a query to run more slowly than on a 32-bit platform. However, on very large systems, the increased overhead may be more than compensated for by improved data access provided by larger caches, giving you an overall performance improvement.

Q: How long will Sybase continue to support 32-bit ASE?

A: At this time, Sybase continues to support 32-bit platforms. The new ASE 12.5 release will have both 32- and 64-bit versions. In general, Sybase offers support for the current ASE version and the previous version. If Sybase should determine that it can no longer support a version or platform, an "End-Of-Life" announcements is sent out, typically about a year in advance of the end of support. To see recent EOL notices, go to the Technical Documents collection on the Sybase Web site.

Q: How do I upgrade to 64-bit ASE?

A: You can upgrade an existing 32-bit server to a 64-bit version using several procedures. If you are on a version of 32-bit ASE lower than 12.0 (11.0.3, 11.5.1, or 11.9.2) you can plan your migration as a normal migration, using sqlupgrade or by dumping and loading user databases into a new server. If you are on a 32-bit version of ASE 12.0 and you want to migrate to 64-bit ASE 12.0, you cannot use sqlupgrade. See the TechNote Migrating from ASE 12.0 32-bit to ASE 12.0 64-bit for more information on how to do this.

Q: Are dumps between 32-bit and 64-bit ASE compatible?

A: ASE supports dumps between 32-bit and 64-bit servers in either direction. The exception is the master database, because ASE stores 64- or 32 bit-specific information in the config block of the master device.

In addition, an access problem can occur when you dump and load user databases with partitioned tables between 32- and 64-bit platforms. To work around the problem, run the command update partition statistics immediately after performing the load.

Q: Can I migrate to 64-bit ASE by loading a database with a dump from 32-bit ASE?

A: Yes, you can. There is a known problem with this migration path when partitioned tables are involved (see the previous answer).

Q: If I migrate to 64-bit ASE and then decide to roll back, can I load a dump from my 64-bit server back into my old 32-bit server?

A: You can load a 64-bit dump onto a 32-bit server. However, once your installation has been upgraded to 64-bit, you cannot downgrade to a 32-bit installation simply by switching to the 32-bit binary. You must preserve or re-create your 32-bit installation.

Q: Can I replicate between 32-bit and 64-bit versions of ASE?

A: Yes. Sybase Replication Server replicates transactions and does not care about the internal data structures or disk layout of the data server. Replication Server can provide an alternative method to migrating data and transactions from a 32-bit to 64-bit ASE.

Warning for Solaris

This warning applies to Sun platforms only. If you:

you must perform a workaround in order to ensure that your passwords will work in the new system. Before performing the migration to 64-bit ASE, drop and recreate all user passwords on the 32-bit system, using the same or different passwords as you prefer.

This problem (CR 222757) is due to Sun encryption changes in recent releases; The fix to this problem is going to be available in ASE ESD 1, scheduled for early June.

Back to Top
© Copyright 2010, Sybase Inc.