Re: To Sql Server???
- From: Jared Still <jkstill@xxxxxxxxx>
- To: vlado@xxxxxxxxxx
- Date: Thu, 26 May 2005 07:59:06 -0700
The lack of concurrency will cause major changes to the application.
SQL Server apps tend to require a lot of temporary tables for reporting
purposes, as the data can change while it is being read.
Not a recipe for success.
Is there a business case for this move to SQL Server?
I doubt that it's price. MS does not give this product away.
For some licensing situations it may be less than Oracle, but
not enough to make it worthwhile to rewrite an app.
You can't really 'port' this to SQL Server. It is a rewrite.
On 5/26/05, Vlado Barun <vlado@xxxxxxxxxx> wrote:
>
> 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 asktom.oracle.com <http://asktom.oracle.com>
>
>
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
--
//www.freelists.org/webpage/oracle-l
Other related posts:
