ETL面试问题？
5天后我要去ETL面试。这是我第一次接受关于这个主题的采访。我会被问什么问题？它们很可能与 MS SQL Server 集成服务有关。 如果可能，请提供答案。 =)
In 5 days I'm going to ETL interview. It's my first interview on this subject. What question would I be asked? Most likely they will be about MS SQL Server Integration Service.
If possible, provide the answers. =)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果有必要，请保持高水平，但不要问自己无法回答的问题。
我同意布拉德的观点，即语法并不重要，重要的是思维过程。
另一个想法是询问他们将如何收拾行李并搬迁办公室。它使您能够深入了解 ETL 中所需的同类决策（准备、实际移动内容和验证），并且您可能会更愿意谈论这些而不是 SSIS 的详细信息
Keep it high-level if you have to, but don't ask a question that couldn't answer yourself.
I agree with Brad that syntax is not important, it's the thought process.
Another idea is to ask them about how they would pack up and move an office. It gives you insight into the same kinds of decisions needed in ETL (prep, actual moving of stuff, and validation), and you might be more comfortable talking about that than the details of SSIS
实际思考一下。向他们提供可能需要导入的示例文件的打印输出（可能经过简化以节省时间）。让他们谈论数据库设计、注意事项、关注点以及改进数据的可能方法。然后拿出第二份以某种方式相关的打印输出，看看他们是否能弄清楚如何验证另一个打印输出。
确保您谈论有多少时间可用于根据业务规则和环境执行 ETL 流程。
需要尽可能多的伪代码，但我个人赞成语法可以廉价地教授的想法，但学习如何思考是一件非常昂贵的事情;有时甚至不成功。
另外，询问他们如果要设计源数据的最佳布局，他们将实施什么标准。确保考虑公司之外的数据分发（如果适用）。
Think practically. Hand them a printout of a sample file that might need to be imported (possibly simplified to save time). Have them talk about database design, considerations, concerns, possible ways to improve the data. Then bring out a second printout of somehow related and see if they can figure how to validate the one from the other.
Make sure you talk about how much time is available to perform the ETL processes based on business rules and environment.
Require as much pseudo-code as you like, but I personally subscribe to the idea that syntax can be taught cheaply, but learning how to think is a very expensive thing to teach someone; and sometimes it's not even successful.
Also, ask them what standards they would implement if they were to design the optimum layout of the source data. Make sure you consider data distribution beyond your company (if applicable).