oracle pl / sql - > sql server [英] oracle pl/sql -> sql server

问题描述

你好，


我是一个SQL服务器新手。我们公司有一个大量的应用程序

用PL / SQL编写。我需要将它的一部分移植到SQL Server。


- 我应该选择哪个SQL服务器版本，以便有合理的机会

移植？


- 你能推荐一些最佳实践，工具吗？我在Oracle上使用Toad for SQL

开发，我正在寻找类似于SQL

服务器的东西。


问候，


Hegyvari Krisztian

解决方案

最新的MSSQL生产版本是2000; 2005年将在11月初发布

。你选择哪一个取决于你在2005年找到这些功能的方式，以及你对于移植到第1版产品有多么谨慎。

。但是，考虑到MSSQL 2000已经有5年左右的时间了，那么考虑到2005年，它肯定值得花一两块钱。


您可能应该花些时间查看产品信息

，其中包括移植指南和移植工具

Oracle：

http://www.microsoft.com/sql/default.mspx


与任何重要的迁移一样，工具只会带你到某个特定点 - 移植DDL和数据可能相对简单，

但是程序代码是另一回事，所以你应该准备好手工完成一定数量的工作。当然还有使用全新架构的所有

问题，能够运行/监控/备份等新平台，安全模型等。


如果你的公司以前没有使用MSSQL的经验，那么它可能值得寻找拥有的人，否则就有了/>
a很有可能迁移不会成功（或者可能是b $ b功能但执行不可接受，没有强大的安全性等）。

就个人而言，我不相信将应用程序移植到我不知道的

平台上，并且您的管理层需要了解该方法所涉及的风险。


Simon

prunoki写道：

你好，

- 我应该选择哪种SQL服务器版本，以便有合理的移植空间？

- 可以你推荐任何最佳实践，工具？我在Oracle上使用Toad进行SQL开发，我正在寻找类似SQL的服务器。

问候，

Hegyvari Krisztian

取决于您所说的端口一词的含义我建议你不要

这样做。


如果您的Oracle应用程序使用序列... SQL Server没有

他们。如果您的Oracle应用程序使用全部触发器......

SQL Server没有它们。如果您的Oracle应用程序使用了许多不同的表和索引类型...... SQL Server没有它们。如果

您的应用程序采用Oracle事务模型，锁定模型，

和读写一致性...... SQL Server没有它们。


基于Oracle

版本重写应用程序以利用优化SQL Server的功能会好得多。

People尝试移植，无论哪种方式，几乎总是制造大的昂贵的

混乱。


在读取不会阻止写入的环境中构建的应用程序

和写不要阻止读取的情况非常糟糕，并且没有b
$ b具有相同的架构。

-

Daniel A. Morgan
http://www.psoug.org
da******@x.washington.edu
（将x替换为x以回复）

" Simon Hayes" < sq*@hayes.ch>在消息中写道

news：11 ********************** @ o13g2000cwo.googlegr oups.com ...

最新的MSSQL生产版本是2000; 2005年将于11月初发布。您选择哪一个取决于您在2005年如何找到功能，以及您对移植到第1版产品的谨慎态度。但是，鉴于MSSQL 2000已经有5年左右的时间了，考虑到2005年肯定值得。


另外，鉴于SQL 2005有几个设计变更具体是针对它的b $ bb承担甲骨文 （比如对事务并发的更改）我会用SQL 2005来支持
。


此外，MS在他们的网站上有一个产品（我不是''' t召回确切的URL）

将把Oracle应用程序和端口带到SQL Server。


就个人而言，我不相信任何工具可以做更多而不是

架构的基本端口。我仍然会检查你的所有代码，以确保它在SQL Server上以类似的方式工作，就像在Oracle上一样（并发性很强，

序列另一个）。


如果你的公司以前没有使用MSSQL的经验，那么它可能值得寻找拥有的人，否则就有了>很有可能迁移不会成功（或者它可能是功能性的，但执行起来不可接受，没有强大的安全性等）。
就我个人而言，我不会对将应用程序移植到<我不知道的平台，你的管理层需要了解这种方法所涉及的风险。


我会想到这一点。


Simon

Hello,

I am an SQL server newbie. Our company has a massive application
written in PL/SQL. I need to port parts of it to SQL Server.

- Which SQL server version should I choose, to have a reasonable chance
of porting?

- Could you recommend any best practices, tools? I use Toad for SQL
development on Oracle, I am looking for something similar for SQL
server.

Regards,

Hegyvari Krisztian

解决方案

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.

You should probably spend some time reviewing the product information
here, which includes migration guides and tools for porting from
Oracle:

http://www.microsoft.com/sql/default.mspx

As with any significant migration, tools will only take you to a
certain point - porting DDL and data may be relatively straightforward,
but procedural code is another matter, so you should be prepared to do
a certain amount of work by hand. And of course there are all the
issues of working with a completely new architecture, being able to
run/monitor/backup etc a new platform, the security model etc.

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.

Simon

prunoki wrote:

Hello,

I am an SQL server newbie. Our company has a massive application
written in PL/SQL. I need to port parts of it to SQL Server.

- Which SQL server version should I choose, to have a reasonable chance
of porting?

- Could you recommend any best practices, tools? I use Toad for SQL
development on Oracle, I am looking for something similar for SQL
server.

Regards,

Hegyvari Krisztian

Depending on what you mean by the word "port" I would suggest you not
do it.

If your Oracle application uses sequences ... SQL Server doesn''t have
them. If your Oracle application uses the full range of triggers ...
SQL Server doesn''t have them. If your Oracle application uses many
different table and index types ... SQL Server doesn''t have them. If
your application assumes the Oracle transaction model, locking model,
and read-write consistency ... SQL Server doesn''t have them.

It would be far better to rewrite the application based on the Oracle
version to take advantage of optimizing SQL Server''s capabilities.
People that try to port, either way, almost always make big expensive
messes.

An application built in an environment where reads don''t block writes
and writes don''t block reads will fare very poorly in one that doesn''t
have the same architecture.
--
Daniel A. Morgan
http://www.psoug.org
da******@x.washington.edu
(replace x with u to respond)

"Simon Hayes" <sq*@hayes.ch> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.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

这篇关于oracle pl / sql - &gt; sql server的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！