将数据从 SAP 传输到 SQL Server 的最佳方式是什么? [英] What is the best way to transfer data from SAP to SQL Server?

问题描述

我们希望基于 SAP 表从头开始构建一个新的数据仓库.对于提取、转换和加载 (ETL) 过程，我们希望使用 Microsoft SQL Server 集成服务.市场上有许多供应商，如 Theobald、CData 等，它们提供了访问 SAP 数据的框架.但是，SAP 本身也提供了一个 SAP .NET Connector 3.0，用于通过 RFC 访问数据.

We want to build up a new Data Warehouse from scratch, based on SAP Tables. For the extract, transform and load (ETL) proedure, we want to use Microsoft SQL Server Integration Services. There are many vendors on the market like Theobald, CData etc, which provide a framework to access SAP data. But there is also a SAP .NET Connector 3.0 provided from SAP itself to access the data via RFC.

您对这些不同的解决方案有什么经验吗?根据 DWH 概念，我们只想访问表，并专注于 SAP 数据的快速传输(良好的传输性能).

Do you have any experiences with these different solutions? According to the DWH concept we just want to access the tables and are focused on fast transfer (good transfer performance) of the SAP data.

感谢您的帮助.

推荐答案

我更愿意坚持使用原生 SAP 解决方案.以下是选项:

I'd prefer stick to the native SAP solutions. Here are the options:

1. SAP SLT非常简单但有效的解决方案.功能非常有限(没有连接，没有来自多个源的合并)，但似乎是一次性转换的理想选择.
2. SAP 数据服务 (SAP BODS)更复杂的工具，允许构建场景从任何来源到任何目的地的 ETL，包括复杂的转换、脚本等.
3. SAP MDM/千年发展目标更多概念性的解决方案，包括数据质量、数据治理、验证、重复数据删除等.MDM 和 MDG 实际上是两种不同的产品，但为了简单起见，我们将它们放在一起.它们大概用于 SAP 系统之间的即时复制过程，但 MDM 更通用，可以独立使用，也可以用于任何数据源.
4. SAP PI最先进、功能最丰富且最复杂的解决方案，似乎不是一次性传输的合理选择.详细了解差异.
5. SAP 数据中心适用于大数据源的 SAP 解决方案，对于您的案例来说似乎是多余的.

1. SAP SLT Very simple but efficient solution. Features are quite limited (no joins, no merging from multiple sources) but seems to be ideal for one-time transformation.
2. SAP Data Services (SAP BODS) More sophisticated tool that allows building scenarios of ETL from any sources to any destinations, including complex transformations, scripts, etc.
3. SAP MDM/MDG More conceptual solution which includes data quality, data governance, validation, de-duplication, etc. MDM and MDG are actually two different products but here we place them as single for the sake of simplicity. They are used presumably for instant replication process between SAP systems, but MDM is more versatile and can be used standalone, and for any data source.
4. SAP PI The most sophisticated, feature-rich and complex solution which doesn't seem reasonable choice for 1-time transfer. More about differences.
5. SAP Data Hub SAP solution for Big Data sources which seems redundant for your case.

这完全取决于您的任务范围(镜像、复制或转换)、数据的复杂性、必要的转换(简单或复杂)、周期性(临时或即时)、预算等.

It's all depends of the scope of your task (mirroring, replication or transformation), complexity of data, necessary transformations (simple or complex), periodicity (ad-hoc or instant), budget and others.

如果您只需要将 DWH 按原样移动到 MS SQL 中，我建议使用 SLT 作为最高效的方式.如果您需要更复杂的转换，我建议使用 SAP BODS.其他点似乎与您的任务无关.

If you just need to move your DWH as is into MS SQL I suggest to use SLT as the most performance-efficient way. If you need more sophisticated transformations I suggest using SAP BODS. Other points seems not relevant for your task.

这篇关于将数据从 SAP 传输到 SQL Server 的最佳方式是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！