迁移一个窗口最好的办法形成从SQL Server到Oracle应用 [英] best way to migrate a windows forms application from sql server to oracle

问题描述

我找迁移Windows窗体从MS SQL服务器的Oracle应用程序的最佳途径。该表架构重新在Oracle媒体链接，数据被复制到Oracle表。应用程序使用ADO.NET数据集来访问数据库。所以，我应该只是一种替换所有引用的SqlDataAdapter与OracleDataAdapter，SqlConnection的用的OracleConnection等在自动生成的DataTableAdapters code，或者是有一些其他的方式，使现有的数据访问code与Oracle的工作？

I looking for a best way to migrate a Windows Forms application from MS SQL Server to Oracle. The table schema is recreated in oracle allready and the data was copied into Oracle tables. The App uses ADO.NET Datasets to access the DB. So, should I just kind of replace all references to SqlDataAdapter with OracleDataAdapter, SqlConnection with OracleConnection etc. in the autogenerated DataTableAdapters code, or is there is some other way to make the existing dataaccess code work with Oracle?

推荐答案

有一个在我的答案在这里：的 MVC3和实体框架

Have a look at my answer here: mvc3 and entity Framework

其实分层和分离关注这个逻辑也适用于MVC，的WinForms，WPF，SL等等...在这样的层次堆栈只有DAL（数据访问层）的影响，并需要更新，一切保持不变。

in fact this logic of layering and separation of concerns applies to MVC, WinForms, WPF, SL and so on... in such layered stack only the DAL (Data Access Layer) is impacted and needs to be updated, everything else stays the same.

我的建议是让别的不说这样的DAL类库分离，并在那里，正如你所说，你应该替换的SqlConnection 和的SqlCommand 与Oracle的。

my suggestion is to make such DAL class library separated from anything else and in there, as you mentioned, you should replace SqlConnection and SqlCommand with the Oracle ones.

这篇关于迁移一个窗口最好的办法形成从SQL Server到Oracle应用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！