SQL Job taking more time to execute
Hi, I have a ssis package that is scheduled in sql server 2005 in development as well as production. Now the thing is that the job in development is taking normal time say 10 mins to execute. The job in production is taking more time to execute say around 40 mins and some times 3 hours to execute. Now I want the log files about the job where it is wasting more time in production which is making it execute so slow than development. Its there any way to look into the log in that way. Is there any way to check the loading time of the tables using some kind of log so that i could know the reason behind it. Please suggest. Thanks in advance
August 31st, 2011 8:46pm

Hi, To enable logging in a package, open the package in BIDS, right-click on a clear area of the Control flow of the package, and select Logging. You can log verbose information if you select all events on the package level. I would suggest to log into a simple text file first. For more information about logging in SQL Server 2005 Integration Services, please refer to http://msdn.microsoft.com/en-us/library/ms138020(v=SQL.90).aspx. Kind regards, Zoli-- Zoltn Horvth -- MCITP SQL Server Business Intelligence Developer 2005, 2008 -- MCITP Database Developer 2008, Database Administrator 2008 -- Please mark posts as answered or helpful where appropriate.
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2011 9:39pm

Dear Moderators, please move this question to the SSIS forum. Thank you. -- Zoltán Horváth -- MCITP SQL Server Business Intelligence Developer 2005, 2008 -- MCITP Database Developer 2008, Database Administrator 2008 -- Please mark posts as answered or helpful where appropriate.
August 31st, 2011 9:40pm

Hi Zoltán Horváth, Is there any log that is stored in sql to check the job statistics(Like, time taken to load individual tables etc.,). Its the reason why I posted this in sql forum. Thanks in Advance.
Free Windows Admin Tool Kit Click here and download it now
September 1st, 2011 8:59am

Hi, By default, there is no log with that level of details. But you can turn on logging in your packages, and then select SQL tables (instead of a text file) as the log target. Kind regards, Zoli-- Zoltn Horvth -- MCITP SQL Server Business Intelligence Developer 2005, 2008 -- MCITP Database Developer 2008, Database Administrator 2008 -- Please mark posts as answered or helpful where appropriate.
September 4th, 2011 3:44am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics