SSIS数据流任务无法长时间启动 [英] SSIS Dataflow task not starting for long time

查看:81
本文介绍了SSIS数据流任务无法长时间启动的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个数据流任务,它将从服务器B表中提取记录并将其加载到服务器A表中。我正在使用OLEDB源和OLEDB目标转换。 OLEDB源是依赖于变量的sql查询(表名将在from子句中的运行时更改)。源sql查询大约需要500到1500行。



包在服务器A中部署,

包运行非常好过去六个月,

现在包和数据流任务已启动并显示进度信息,但在OLEDB源转换中它理想的不显示进度信息。



但是,当源查询从服务器A中的SSMS运行时,它在15秒内完成渲染记录,但是程序包需要很长时间超过30分钟且理想情况下不显示进度信息。 />


请指导我修复它,提前谢谢...

I have a dataflow task which going to pull the records from Server B table and load it in Server A table. I'm using OLEDB source and OLEDB destination transformations. the OLEDB source is sql query that depends on variable (table name will be changed at the runtime in the from clause). the source sql query getting around 500 to 1500 rows.

the package is deployed in Server A,
the package runs very good for a past six months,
now the package and Data Flow task is started and showing progress info, but in the OLEDB source transformation its in ideal not showing progress info also.

but, when the source query run from the SSMS in the server A its finished rendering records in 15 seconds, but the package takes long time more than 30 min and its in ideal not showing progress info.

kindly guide me to fix it, thanks in advance...

推荐答案

这听起来像是查询你用于获取数据的效果不是很好。



如果源是SQL Server数据库,找出需要时间的最佳方法是使用 SQL Server Profiler [ ^ ]。配置来自源服务器端的传入呼叫,并查看查询是否是瓶颈。
This sounds like the query you use to get data is not performing very well.

If the source is an SQL Server database, probably the best way to find out what takes time is to use SQL Server Profiler[^]. Profile the incoming calls from the source server side and see if the query is the bottleneck.


这篇关于SSIS数据流任务无法长时间启动的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆