有关帮助从 MySQL 迁移到 MS SQL 的提示
我对数据库开发感兴趣已经有一段时间了，并认为 MS SQL 在 T-SQL 方面可以提供很多功能，并且通常具有更多功能（并不是说 Oracle 或 Postgres 没有这些功能）。
我想知道：
- 我所经历的重大范式变化是什么？ 应该期待看到什么？
- “正规”企业付出了多少努力 开发他们的数据库（用于 事务、触发器、事件、数据 清洗、ETL）？
- 我能期待什么 来自 MS SQL 的内部工作原理 开发团队以及他们如何 与 .NET 应用程序交互 开发商？
我希望我正确地表达了我的问题。 我对整个 .NET 场景不太了解。
I have been interested in database developing for some time now and decided that MS SQL has a lot to offer in terms of T-SQL and generally much more functionality (not saying that Oracle or Postgres don't have that).
I would like to know:
- What are the big paradigm changes I
should expect to see? - How much effort do "regular" companies put
into developing their database (for
transactions, triggers, events, data
cleansing, ETL)? - What can I expect
from the inner-workings of MS SQL
developer teams and how they
interact with the .NET application
developers?
I hope I have phrased my question correctly. I am not very clued-up about the whole .NET scene.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
无法回答#1，因为我从未使用过 mysql，但我会尝试回答#2 和#3。
这往往取决于数据库的大小和/或公司的规模（或专业水平）。 拥有大量用户的大型数据库的公司确实花费了大量时间来确保数据库的完整性和性能调整。 如果他们不这样做，他们就会失去客户。 我们有 6 名除了 ETL 工作什么也不做的人，还有 5 名负责调整和管理数据库和数据库服务器的数据库管理员，以及许多编写 t-sql 代码的开发人员。
就第三点而言，在优秀的公司中，这些人作为一个团队可以很好地合作。 在糟糕的公司中，两个群体之间经常存在紧张关系，并且无论发生什么问题，每个群体都将对方作为替罪羊。 我与一群优秀的 .net 开发人员一起工作。 他们尊重我的数据库专业知识，就像我尊重他们的 .net 专业知识一样，我们就设计问题和调优问题以及一般需要双方输入的任何问题互相协商。
Can't answer #1 as I've never worked with mysql but I'll take a shot at #2 and #3.
This tends to depend on the size of the database and/or the size (or professionalism) of the company. Companies with large databases with many users spend a great deal of time indeed making sure that the database both has integrity and is performance tuned. They woudl lose customers if they did not. We have 6 people who do nothing but ETL work and 5 dbas who tune and manage the databases and database servers as well as many many developers who write t-sql code.
As far as #3, in good companies these people work together very well as a team. In bad companies, there is often tension between the two groups and each uses the other group as a scapegaoat for whatever problems occur. I work with a bunch of great .net developers. They respect my database expertise as I respect their .net expertise and we caonsult each other on design issues and tuning issues and in general any issue that needs input from both sides.
http://forums.mysql.com/read.php?60,124480, 124480 详细介绍了如何使用从 SQL Server 到 MySQL 的链接服务器来进行实际的数据迁移。
http://forums.mysql.com/read.php?60,124480,124480 details using linked servers from SQL Server to MySQL to do the actual data migration.
Apache DDLUtils 应该能够提供帮助。 您可以将架构逆向工程为通用 DDL，并将数据导出到平面文件。 之后导入即可。
Apache DDLUtils should be able to help. You can reverse engineer the schema into a common DDL and also export the data to a flat file. Import it in afterward.