We have jobs which uses xp_cmdshell to execute a package. These jobs are working fine in SQL Server 2005 environment, but in SQL Server 2008 some of these jobs takes more time to complete. One particular job which takes 1.5 hours in sql server 2005 now takes around 5 hours to complete. When i looked in the activity monitor I could see the sql agent is waiting with the wait type preemptive_os_pipeops. I haven't seen this before and when searched I found this one was a new wait type in SQL Server 2008. I would like to know why the execution takes much longer time in sql server 2008 and how to avoid this wait type.Karthikeyan Chennai

Hello, Please check this link http://connect.microsoft.com/SQLServer/feedback/details/556545/hung-connection-wait-type-preemptive-os-pipeops You can schedule your package by using SQL Server agent if your company don't have restriction not to use SQL Server Agent. Thankshttp://sqlage.blogspot.com/

The package is executed as a scheduled job in sql server agent. But the job uses xp_cmdshell command to run the SSIS package.Karthikeyan Chennai

Hi KarthikSpeaks: Please refer to the following articles, and then check if it works for you. Debugging slow response times in SQL Server 2008: http://blogs.technet.com/b/sqlos/archive/2008/07/18/debugging-slow-response-times-in-sql-server-2008.aspx BCP hangs with Preemptive_os_pipeops: http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/1b48cde7-409e-4d51-9a4c-73e9e3d24f6d More over, I suggest you can post the question to our SQL Server Tools General forum: http://social.msdn.microsoft.com/Forums/en-US/sqltools/threads, there are many experts focus on it. Thanks, Eileen