Sybase products are generally perceived within the database administrator (DBA) community as very reliable and easy to maintain, particularly compared to Oracle. Any move from Sybase to other DBMS (database management system) have got to be justified in terms of the current level of dissatisfaction with Sybase and the level of desire to use other. I cannot recall anywhere where this is valid.
The latest Sybase flagship product, ASE 15, has filled much of the perceived functionality gap between ASE and other databases.
Linux is an ideal and cost-effective platform for development teams and many companies. With the availability of heterogeneous dump and load of Sybase databases across different operating systems, Sybase — by virtue of its modularity and ease of use — is an ideal DBMS for Linux. This needs to be contrasted with Oracle which is, pound for pound, a far heavier beast and resource-hungry.
Sybase has a well-established and skilled workforce, offering infrastructure and development teams who are fully familiar with database architectures and Sybase products.
Applications developed using Sybase have been running for a while and providing adequate service. There is absolutely no guarantee that migrating these applications to another DBMS will result in the same level of service. I know of no case where a migration from Sybase to Oracle or otherwise has resulted in a noticeable performance gain.
The exit barriers from Sybase and the entry barriers to others are high. For a medium-to-large application, it will take an average of 10 years for investment for ROI. A simple cost/benefit analysis will verify this statement.
Check our Sybase ASE 15’s total cost of ownership (TCO) compared to Oracle. Based on my clients’ experience, one requires 2.5 Oracle DBAs to provide the same level of service as a single Sybase DBA.
Sybase is fairly modular and has a simple syntax. Contrast this with Oracle where, in most cases, you require a third-party product to allow the DBA to reduce his/her workload. Perhaps that may be a reason why TOAD, a non-Oracle product, is the most popular GUI interface for Oracle!
Since Sybase is a very secure database. In fact, it is a favourite with the U.S. Department of Defense and Central Intelligence Agency. Sybase is quickly bringing the security features — such as extensive Kerberos support, programmable authentication and data encryption — to the market.
SAP’s release of its lightway product for Sybase on Linux and IBM’s steps towards selling their line of P5 Linux servers with ASE, while they have DB2 and Informix themselves, are pretty strong statements about the future of Sybase.
The future of Sybase is secure, largely because it is well entrenched in its core marketplace, the financial services market. More than half of Wall Street runs on Sybase. The majority of complex trading systems and banks use sophisticated replication technology to provide publisher-subscriber or peer-to-peer replication. At this juncture, none of the competitors can provide the same degree of functionality that Sybase Replication Server provides.
Both Oracle and Sybase provide a range of database-related products. The following list illustrates how the main high-level Oracle products compared to Sybase products. While this list is deliberately kept brief, it provides some basic guidance on how Oracle and Sybase can be aligned.
Oracle Database Server
Sybase ASE (Adaptive Server Enterprise)
Oracle OLAP and DW
Sybase ASE Cluster Edition
Oracle Times Ten
Sybase ASE In-Memory Database
Oracle Streams/Golden Gate
Sybase Replication Server
Oracle Data Guard
Sybase Mirror Activator/Sybase Replication Server
About Sybase ASE Sybase ASE is the database that powers Wall Street. ASE has been delivering rock-solid reliability and top-level performance for the past 25 years. Sybase ASE has a lower total cost of ownership than Oracle, and delivers better performance on the same hardware. Sybase ASE is ready to be the database in any application that runs on Oracle today.
In the vein, SAP also announced Wednesday that high-profile customer Procter & Gamble is “planning to migrate its existing SAP ERP environment to ASE database.” P&G currently runs SAP on Oracle, and it also uses Oracle Exadata for data warehousing. If P&G follows through with this plan, it would be a financial blow and, more significantly, a big symbolic blow to the industry’s biggest database supplier.
They have migrated their SAP based Oracle driven Analytical Servers on to Sybase ASE 15.7. The POC has been done for migrating 13 TB of data and more to happen yet.
Anurag has more than 6+ years of experience in Sybase Database Development .His Area of expertise includes Performance, Query Optimization, Cost Optimization, TSQL Development. He is also involved in Consultancy to Financial Firms for Database Implementation and Maintenance. He has supported many Global Financial firms and recently started a new portal -Mati Rang. AnVa (Founder) has more than 6+ years Exp in Sybase ASE/REP Database Administration. His area of interest is ASE Implemenation and maintenance , Performace Tunning , Sybase HA ,Shared Cluster and Replication. Also exploring the In-Memory Databases (HANA) , Big Data, Hadoop and Java. He is also supporting the Forum Sybase Team and started this sybaseblog.com in late 2009. Andrew is Guest Blogger on sybaseblog.com. Andrew have been working with Sybase for more than a decade: ASE & RS mostly.
He has written lot of tools that help to manage/monitor the system for ASE and Replication and some tools are on the way..
He is also poet and love to be creative all the way.
This Blog is neither sponsored by nor in any way affiliated with SAP & Sybase,Inc. In any case, neither any authors nor SAP & Sybase Inc assumes any responsibility for errors in the blog postings, nor do they have any liblilties for damages resulting from the use of blog postings.If you are using any Supported & Unsupported commands/features listed in blog, this is completely on your(user) risk, sybaseblog.com not having any libilitiy.
This blog is only for sharing purpose. The opinions expressed here represent bloggers own and not those of their any past and present employer.