Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: To Sql Server???

RE: To Sql Server???

From: Vlado Barun <>
Date: Thu, 26 May 2005 10:20:11 -0400
Message-Id: <>

One of the major differences between SQLServer and Oracle is the Concurrency Control. See Tom Kyte's Expert One-on-One book, pg 123 - 133 and do a search on

In summary, you can't just translate your PL/SQL procs and triggers to T-sql. You have to recode the way the data is accessed to compensate for the difference in the Concurrency control between SQLServer and Oracle. Unless, of course, your management doesn't care about performance and scalability...

And don't forget, there are many other differences you will have to worry about...

Vlado Barun, M.Sc.
Senior Data Architect, Cadre5

-----Original Message-----

From: [] On Behalf Of Kline.Michael
Sent: Thursday, May 26, 2005 10:04 AM
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.  

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.  

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.  

Still "That doesn't matter. We have willed it to be Sql Server."  

I don't think this is going to happen, and HEAD management has "cleaned house" with middle management before.  

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."  

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.  

(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.)  

Michael Kline   

The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer.   

Seeing Beyond Money is a service mark of SunTrust Banks, Inc.   




-- Received on Thu May 26 2005 - 10:25:03 CDT

Original text of this message