SSIS：“增量”进口？ [英] SSIS: "Incremental" import?
问题描述
我必须实现一个加载三个不同数据库，转换数据并将其结果加载到新SQL数据库的进程。
I have to implement a processus that load three different database, transform data and load it's results into a new SQL database.
我想到了SSIS（集成服务的SQL服务器）。这对我来说是完美的，但是：这个过程将在每个晚上6-8个月运行。它必须只导入更改。
I thought to SSIS(Integration services of SQL server). It would be perfect for me, but: this processus will run during 6-8 month, every night. It has to import only changes.
我不知道我是否可以使用SSIS执行此操作？
And I don't know if I can do this with SSIS?
要导入大量数据，因此我们希望这些数据以递增方式更新（基于源数据库中的ModifiedAt列）。
There is a big volume of data to import, so we want that those data are updated incrementally(Based on the "ModifiedAt" column on source database).
所以：
- 这是可能的（增量导入），怎么样？
- 如果是：什么是最好的每天安排它的方式？
- 如果没有：你能看到另一种方法，我不必从头开始编程吗？
推荐答案
是的，@ andyLeonard有一个很棒的系列名为集成服务的阶梯我经常在答案中引用这一系列文章，因为它更简洁，然后尝试在单个答案中将SSIS标记的累积智慧串起来。在该系列文章中，Andy将向您介绍增量加载模式的各种内容。我认为这将为您提供一些如何构建导入的清晰度。
Yes, @andyLeonard has an excellent series called the Stairway to Integration Services I reference this series of articles frequently in answers because it's much more concise then trying to string together the accumulated wisdom of the SSIS tag in a single answer. In that series of articles, Andy walks you through various takes on the incremental load pattern. I think that will give you some clarity on how to structure your imports.
您可以使用组织当前使用的任何计划工具来安排SSIS包。
You can schedule SSIS packages using whatever scheduling tool your organization currently uses.
-
SQL Agent - SQL Server的内置调度工具是组织的常用选项。您的DBA已经在使用它来处理索引重建/重组等事情的安排，这很有可能。使用Agent的一个优点是，对于初学者来说，它有一个仅为运行SSIS包而构建的步骤。并不是说启动一个SSIS软件包并不是很复杂，但是每一点都有帮助。
SQL Agent - the built in scheduling tool for SQL Server is a common option for organizations. Odds are strong that your DBAs are already using it to handle scheduling of things like index rebuilds/reorganization, etc. A plus to using Agent is that for the neophyte, it has a step built just for running SSIS packages. Not that it's all that complicated to launch an SSIS package but every little helps.
Windows调度程序 - Windows内置了一个可维护的调度程序（名称包括我， at 也许？）。如果您正在使用这种方法，我可能建议您创建一个简单的批处理脚本来启动程序包，这样您就可以确保程序包的手动启动与调度程序运行的相同。
Windows scheduler - Windows has a serviceable scheduler built in (name eludes me, at maybe?). If you're using this approach, I'd probably suggest you make a simple batch script to start the package, that way you can ensure a manual launch of the package is the same as what the scheduler runs.
潮汐我在哪里，我们使用Tidal来处理我们的所有工作安排。它并不便宜，但在我们试图协调大型机，unix和Windows环境中的活动的环境中，它是蜜蜂的膝盖。界面是一个令人难以置信的java东西，我很想看到它在火中死了几次但是不要让你分心你的工具的能力。
Tidal Where I'm at, we use Tidal to handle all our job scheduling. It's not cheap but in an environment where we are trying to coordinate activities across mainframe, unix, and windows environments, it's the bees knees. The interface is a god-awful java thing that I'd love to see die in a fire a few times over but don't let that distract you from the capability of the tool.
这篇关于SSIS：“增量”进口？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
