Should You Migrate from Sybase to SQL Server?
|
This white paper will provide you with distinct examples of the total cost of ownership (TCO) associated with staying with Sybase ASE as compared to migrating to Microsoft SQL Server 2005. This white paper examines the TCO implications of a 32-bit database deployment and how costs change as one adds:
| • | An upgrade to Sybase ASE 15 |
| • | Two-node clustering |
| • | Integrated business intelligence |
In addition, this white paper examines the TCO of a 64-bit implementation and the change in costs as one upgrades to Sybase ASE 15 and adds clustering.
This white paper estimates TCO by combining independent third party data on Sybase ASE and Microsoft SQL Server 2005, with the analysis engine at the heart of CIOview’s TCOnow! for 32 and 64 Bit Databases. Reviewing the TCO of Sybase ASE as compared to SQL Server 2005 reveals a number of important findings:
| • | The economics of Sybase and SQL Server 2005 are surprisingly consistent for both 32-bit and 64-bit systems. |
| • | Remaining static is not an economical option. |
| • | Total cost of ownership is one of the best methods to fully account for the costs of operating any database. |
| • | The extensibility of Sybase ASE and SQL Server 2005 are very different when it comes to Business Intelligence. |
| • | Hardware and operating system platform differences can have multi-million dollar cost differences when you add elements such as clustering. |
Note The .pdf file is over four megabytes (MB) in size. For better performance, you can right-click the link and choose Save Target As to download the file to your local computer rather than browsing it online.
