![]() | |
#1
| |||
| |||
|
|
After using Sybase for the longest time, I changed to Oracle... It's fabulous! # New York investment banking powerhouse PaineWebber announced # its switch of nearly 500 databases from Sybase to Oracle # Corporation technology. # # After an intensive 15-month assessment that compared IBM, # Microsoft, Oracle, and Sybase database server software, # PaineWebber selected Oracle, declaring that it will install Oracle # servers in each of its 385 branches, plus an additional 100 # servers in its main office to support data for 25,000 users in # its e-commerce, private client, foreign exchange, and trading # applications. # # "Oracle will provide a solid foundation for all of our # applications companywide," says Eric Rabinowitz, PaineWebber's # corporate vice president of data resource management. It "speeds # time-to-market for emerging e-commerce services, which will in # turn help our financial advisers better serve their clients' # needs." |
#2
| |||
| |||
|
|
Daniel Morgan <damorgan@x.washington.edu> wrote: Gay Male Anthony Mandic wrote: After using Sybase for the longest time, I changed to Oracle... It's fabulous! I agree. But putting aside the marketing hyperbole ... it is a major change in concepts and architecture and should not be undertaken without a thorough understanding of the major differences (far more than just syntax) between the two products. Hmmm, Apple has a "switch" program for Windbloze lusers, etc. Is there any decent functional characteristics documentation for moving to Oracle from Sybase? Oh, Oracle does have "Sybase Conversion Kits" to translate schema, stored procedures, and export (BCP to flat) / import Oracle. That document says they'd be glad to have their consultant division help youz. |
#3
| |||
| |||
|
|
Gay Male Anthony Mandic wrote: Daniel Morgan <damorgan@x.washington.edu> wrote: Gay Male Anthony Mandic wrote: After using Sybase for the longest time, I changed to Oracle... It's fabulous! I agree. But putting aside the marketing hyperbole ... it is a major change in concepts and architecture and should not be undertaken without a thorough understanding of the major differences (far more than just syntax) between the two products. Hmmm, Apple has a "switch" program for Windbloze lusers, etc. Is there any decent functional characteristics documentation for moving to Oracle from Sybase? Oh, Oracle does have "Sybase Conversion Kits" to translate schema, stored procedures, and export (BCP to flat) / import Oracle. That document says they'd be glad to have their consultant division help youz. To convert Oracle to Sybase there ae a number of products. But all they do is get you started. Not one of them can turn autonumbering into sequences with before insert triggers. Not one of them can not create temporary tables and create in-line views in their place. Not one can change your code to an environment where reads don't block writes and writes don't block reads. They are starting points ... but after that of little or no value. Some of the worst PL/SQL I have ever seen was from a SQL Server database converted to Oracle by people that thought because it compiled it would run. And run it did. Right into massive data corruption. -- Daniel Morgan http://www.outreach.washington.edu/e...ad/oad_crs.asp http://www.outreach.washington.edu/e...oa/aoa_crs.asp damorgan@x.washington.edu (replace 'x' with a 'u' to reply) |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
There's also a big $ difference, isn't there? When my employer picked a new database platform two years ago (we were a Sybase shop), Oracle was significantly more expensive than DB2 (what they chose). Of course, "Sales" can make the massage the price to make one look more attractive than another. It's the cost-over-time that really matters. "Daniel Morgan" <damorgan@x.washington.edu> wrote in message news:1069635685.726606 (AT) yasure (DOT) .. I agree. But putting aside the marketing hyperbole ... it is a major change in concepts and architecture and should not be undertaken without a thorough understanding of the major differences (far more than just syntax) between the two products. -- Daniel Morgan |
#6
| |||
| |||
|
|
How'd they do that? wrote: There's also a big $ difference, isn't there? When my employer picked a new database platform two years ago (we were a Sybase shop), Oracle was significantly more expensive than DB2 (what they chose). Of course, "Sales" can make the massage the price to make one look more attractive than another. It's the cost-over-time that really matters. "Daniel Morgan" <damorgan@x.washington.edu> wrote in message news:1069635685.726606 (AT) yasure (DOT) .. I agree. But putting aside the marketing hyperbole ... it is a major change in concepts and architecture and should not be undertaken without a thorough understanding of the major differences (far more than just syntax) between the two products. -- Daniel Morgan Depends on what they bought to serve what purposes. If you go to http://store.oracle.com and look up Oracle Standard Edition One you can be fully licensed for under $1000 US. Could DB2 or any other RDBMS be less expensive? Possibly but by how much? If on the other hand your employer bought Enterprise Edition for a 32 CPU OS/390, 9iAS web-application server, a top-line support contract I would expect they'd pay in 7 figures. You can only compare pricing if you know what was compared with what including what features. And one must also leave open the possibility that the employer, not understanding the differences between Standard Edition and Enterprise edition, etc. could have been quoted on far more than was required. Perhaps also the IBM salesperson didn't explain the fact that DB2 has no security other than that provided by the operating system and for $X they would need to purchase Tivoli to come close to the built-in security that comes with Oracle. But even if any single product is more expensive the cost of the RDBMS,itself, is rarely a major part of the TCO. And you must always ask questions such as what features do I need to meet the system's requirements. |
![]() |
| Thread Tools | |
| Display Modes | |
| |