October 19, 2007 at 5:54 am
We have created a SSIS package and we put a schedule using Jobs in SQl 2005. We have handle large number of records almost above 40 lakhs. During run it takes very long to time to execute the package. But if we run the package directly it will take less time. Can any one please help us this long time run in scheduler? Any Idea? Any other way to minimise the run time?
Thanks in advance,
Mano Karnan
October 19, 2007 at 6:12 am
Where is your destination server that is pulling the data thrugh transformations / jobs. My suggestion will be initially through ssbistudio, create a dummy table, run the package and check for the consistency. If it works fine, then there seems to a configuration mis-match while creating the jobs for auto-upload of your data.
October 19, 2007 at 6:13 am
Hi,
One of the possible reasons is "Overlapping Schedules". May be you can check if there is any other job running at the same time, when this job runs....
Renuka__
[font="Verdana"]Renuka__[/font]
October 19, 2007 at 6:20 am
Hi all,
We are having only one Job running on this. Also, we are taking the data from another server (SQL 2000) and the Package & jobs run on another server (SQl 2007). Can you please tell me is there any other possiblilties to slow down?
Mano Karnan
October 27, 2007 at 9:59 am
Check whether Auto shrink option is enabled?
Check the process that is running at the time of job execution and see what are all the process going on the database at the scheduled time.
Since this has happened to us and while checking we found that DBCC jobs are running on the database where insert is also going on.
Regards..Vidhya Sagar
SQL-Articles
November 3, 2007 at 1:19 am
Thanks for u'r reply. I will check and tell the result.
Thanks,
Mano Karnan
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply