数据导出框架或工具

发布于 2024-09-06 07:26:55 字数 143 浏览 2 评论 0原文

.net中有没有数据导出框架之类的。我需要设备一个工具包来将遗留和数据从旧/遗留应用程序导出到正在开发的新应用程序,大约有三个类似的系统。为了让您了解这三个人都有员工表。是否有任何框架或 dsl 工具?或者我必须拿出所有的代码?当您有想要迁移到新产品的客户时,您会如何做?

Is there any data export framework in .net or something. I have need to device a tool kit to export legacy and data from older/legacy application to the new application under development,there are around three similar systems. To give you an idea the three have employee table.Is there any framework or dsl tool for this? Or I have to come up with all the code? How do you do it when you have customers whom you want to migrate to the new product ?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

一花一树开 2024-09-13 07:26:55

从神经网络工具迁移到我们的应用程序后,我可以告诉您,没有“简单的方法”可以做到这一点。每个软件都遵循其自己的内部数据库结构,并且它永远不会与您在设计自己的软件时遵循的相同。

考虑到这一点,最复杂的任务通常分为两个部分:

1) 确定遗留系统中存储的数据什么以及如何。您知道表 PAXNOST 意味着 Patient_Note_Statistic 或类似的东西...一旦您知道数据在哪里(在一个或多个表中)...

2) 导出并清理它:通常,使用 SQL Server 中的导入向导将导致数据因“错误”而无法导入。数据截断、不允许出现空值、格式不正确的日期(例如 01/02/1009)等等。此类问题因迁移而异,但这完全取决于旧系统强制执行(或不执行!)的约束。

如果您设法完成上述所有操作,您可以导入到您选择的数据库(我假设是 SQL Server),然后,当所有数据都在同一个数据库中并且“奇怪的东西”数量最少时,您可以继续使用 T-SQL(或任何其他更自动化的过程,我使用已保存的 T-SQL 脚本,如果需要的话可以重复使用),从 OldTables 移动数据 ->新表。

始终保存您执行的每个脚本。假设您可能必须重新执行所有操作。

始终在“重要步骤”之后备份您的数据库,以便您可以恢复 ->修复->如果必须的话,请重新做。

请记住,您几乎总是必须手动调整某些内容(即: update xxx set yyy = '' where zzz = null; 以及类似的内容以确保约束没问题。同样,这一切都取决于源数据的质量。 始终假设最坏的

情况,您可以在其中执行快速搜索/正则表达式,如果您混合使用 Windows / Unix,请谨慎使用行结尾和字段分隔符(以防万一)。你使用 ASCII 文件,我经常这样做);如果你有这些工具,使用 MS ACCESS 或 MS EXCEL 进行快速表导入/清理也永远不会坏(Excel 每张纸不能超过 65535 行,请记住,使用 Access) )

数据传输对象(DTO)很好,但根据任务的不同,有时它会成为 PITA

Having migrated from NN tools to our application, I can tell you that there’s no “easy way” to do it. Each piece of software follows its own internal database structure and it will never be the same you followed when designing your own.

With that in mind, the most complicated task is usually divided into two parts:

1) Determine what and how is the data stored in the legacy system. You know the table PAXNOST means Patient_Note_Statistic or things like that… Once you have an idea where the data is (in one or more tables)…

2) Export it and sanitize it: More often than not, using an import wizard in SQL server will result in data not being imported due to “errors”. Data truncations, Null values where there shouldn’t be allowed, dates with incorrect format (01/02/1009 for example) and things like that. These kind of problems vary from migration to migration but it all depends upon the constraints the older system enforced (or not!).

If you manage to do all the above, you can import into your DB of choice (SQL server I assume) and then, when all the data is in the same DB and with the minimum number of “strange things”, you can proceed to use T-SQL (or any other more automated process, I use T-SQL Scripts that I have saved and can re-use if I have to), to move data from OldTables -> new tables.

Always save every script you execute. Assume you might have to re-execute it all.

Always back up your db after “important steps” so you can restore -> fix -> re-do if you have to.

And remember that you will almost always have to tweak certain things by hand (I.e.: update xxx set yyy = ‘’ where zzz = null; and things like that to make sure constraints are ok. Again, this all depends upon the quality of the source data. Always assume the worst.

Have a good Text Editor in which you can perform fast searches / regex, be cautious with line endings and field separators if you use a mix of Windows / Unix (in case you use ASCII files, which I often do); also using MS ACCESS or MS EXCEL for quick table import/sanitize is never bad if you have those tools (Excel can’t have more than 65535 lines per sheet, remember that, use Access).

Data Transfer Objects (DTO) is nice, but depending upon the task, sometimes it turns out to be a PITA.

Good Luck.

酒与心事 2024-09-13 07:26:55

如果数据库的架构保持不变,因此要制作更多遗留系统的副本,您可以使用 Visual Studio,它有一个数据菜单项,在该菜单项下您可以启动架构比较或数据比较以将它们从一个服务器到另一个。

格兹,克里斯。

if the schemas of your database stay the same, so making more of an copy of the legacy system, you can make use of Visual Studio which has a Data menu item under which you can start a Schema comparison or Data comparison to transfer them from one server to another.

Grz, Kris.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文