| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: To Sql Server???
One point that has bit me in the behind a couple of times now. People
say their moving to SQL*Server when in fact they mean Microsoft SQL
Server Desktop Edition (MSDE) which is even worse than SQl*server
itself. Basically it's comparable to Oracle Personal Edition, but
really not designed for use outside of the desktop.
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Kline.Michael
Sent: Thursday, May 26, 2005 10:04 AM
To: oracle-l_at_freelists.org
Subject: To Sql Server???
I've got a client who think they are going to take a highly tailored
Oracle subscription system written in UniFace and C and take it to Sql
Server. From the most I can gather, this is going to happen simply
because new management wills it to be so.
=20
This system does subscriptions and of those, there are many, many different types, some with promotions and all sort of highly complex views and triggers and about 40 GB of data.
=20
The system current runs on Oracle 7.3.4 on an old Unix box, and sustains several hundred I/O per second and I've got it tuned that normally they get ZERO data block waits. The vendor is supposedly "almost there" with a version 9 of the product. They also use several specialized products for printing and maintaining zip codes that currently run on the Unix box.
=20
Still "That doesn't matter. We have willed it to be Sql Server."
=20
I don't think this is going to happen, and HEAD management has "cleaned house" with middle management before.
=20
But, what might be key "business case items" to consider in such a move? After all, if this is to be considered "by the will of management" what might be some good "It will" or "It may not work because..." items? Other than the obvious, "If you mess this up, you could bring the company down."
=20
The vendor has mentioned that an Oracle trigger may be 8-15 lines and a similar trigger under Sql Server could be 150-350 lines. (They have some products that do run on Sql Server.) The application has hundreds of triggers, mostly due to UniFace on the client.
=20
(On Oracle this is a very badly coded application that does a lot of full table scans, etc. Fortunately with all the views, I've been able to add indexes and tweak the views, etc.)
=20
Michael Kline=20
=20
*************************************************=20The information transmitted is intended solely=20 for the individual or entity to which it is =20 addressed and may contain confidential and/or=20 privileged material. Any review, retransmission,=20 dissemination or other use of or taking action=20 in reliance upon this information by persons or=20 entities other than the intended recipient is=20 prohibited. If you have received this email in=20 error please contact the sender and delete the=20 material from any computer.=20
*************************************************=20
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Thu May 26 2005 - 13:59:25 CDT
 |
 |