Oracle to Sybase ASE Migration Guide

ORACLE TO SYBASE ASE MIGRATION GUIDERev.1.3and bill have been added as database users. Under each user, a salesdetails table is created, which willhave the full name john.salesdetails and bill.salesdetails.Either option is possible; technically ASE does not favor one over the other, but the multi-tenancy model fits best withASE's methods for backup and restore.It should be noted that multi-tenancy models are sometimes incorrectly seen as security weaknesses since it would beeasier for user bill to access john's tables, since they are located in the same ASE database. This is however not justified:if standard best practices around ASE security are followed, then security can be fully guaranteed.One consideration around multi-tenancy databases is that a backup of a database contains the data from all users in thatdatabase. If this is undesirable, for example because each user wants to have a backup copy of his own database, thenthe first option above (separate ASE databases for each user) should be followed instead.Lastly, it may also be the case that there is only one Oracle schema. In that case, there is no need to qualify the ASEtables with the owner name since they will all be owned by the dbo user.4.6 Schema-related Oracle-Sybase terminologyFollowing is the high-level terminology mapping of Oracle concepts to Sybase concepts. This table is not intended to beused for direct migration purposes, but only as high-level terminology guidance.OracleDatabaseSchemaTablespaceSegmentUndo/rollback tablespaceOnline redo logsSybase ASEDatabase ServerDatabase and objects owned by the same user.Aspects of ASE database and/or database device and/orsegment(system/sysaux tablespaceASE master database;temporary tablespaceASE tempdb database;user-defined tablespacedatabase device and/or segment)A database object that has space allocated (table, index,materialized view)Transaction logTransaction logUser User, Login (see section 5.5)RoleTableTemporary tableRoleTableTemporary tableViewMaterialized ViewClusterIndexIndex-organized tableColumn-level check constraintViewNo direct equivalentNo direct equivalentNon-unique indexTable with clustered indexColumn-level check constraintDatabase Schema Migration 20