|
|
Posted by Greg D. Moore \(Strider\) on 09/14/05 20:16
"Simon Hayes" <sql@hayes.ch> wrote in message
news:1126708309.835154.274220@o13g2000cwo.googlegroups.com...
> The latest production version of MSSQL is 2000; 2005 will be released
> at the start of November. Which one of those you choose depends on how
> compelling you find the features in 2005, and how cautious you are
> about porting to a version 1 product. However, given that MSSQL 2000 is
> already 5 years or so old, it would certainly worth be worth
> considering 2005.
>
Also given that SQL 2005 has several design changes that specifically are
aimed at it "taking on Oracle" (like changes to transaction concurrency) I'd
go with SQL 2005.
Also, MS has a product on their website (I don't recall the exact URL) that
will take an Oracle app and port to SQL Server.
Personally I wouldn't trust any tool to do more than do a basic port of the
schema. I'd still review ALL your code to make sure it works in a similar
fashion on SQL Server as it does on Oracle (concurrency being a big one,
sequences another).
> If your company has no previous experience of working with MSSQL, it
> would probably be worth looking for someone who has, otherwise there's
> a good chance that the migration will not be successful (or it may be
> functional but perform unacceptably, have no robust security etc).
> Personally, I would not be confident about porting an application to a
> platform which I don't know, and your management needs to understand
> the risks involved in that approach.
I would second this.
>
> Simon
>
Navigation:
[Reply to this message]
|