Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 Other SQL Server 2008 Topics
 query time out

Author  Topic 

helpme
Posting Yak Master

141 Posts

Posted - 2013-08-03 : 16:11:47
we have an SSIS package (run from an sql server agent job) that calls stored procedures. When running the stored procedure, the job sits for a while, getting a CXPACKET wait type with the activity monitor indicating the process is blocking itself. After a while, the process finally stops with a 'Query timeout expired' message. We can point the same package to another database on the same instance and the package runs. That would indicate something different in the databases. The execution plans appear to be the same, same indexes, and the stored procedures haven't been changed for a while. (let me add, this process worked a little over a month ago on the database it's having issues with now, don't know what's changed). Anyway, I'm kind of out of ideas to try. Any thoughts would be appreciated.

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2013-08-04 : 10:29:48
are statistics up to date in the problem database? Any recent changes in server configuration?

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/
https://www.facebook.com/VmBlogs
Go to Top of Page

helpme
Posting Yak Master

141 Posts

Posted - 2013-08-04 : 12:59:41
the statistics are up to date. As for the server, both databases are in the same server/instance. I think the issue has to be at the database level. When this process runs (nothing else running on server), it takes the cpu to 99%.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2013-08-04 : 16:53:29
What is different about the two databases? How much data difference is there in terms of rows for the tables involved in this package? Just because they have the same execution plan doesn't mean that the problem database is using the right execution plan. If there are data differences and especially if they are significant, the problem database likely needs a different execution plan and maybe even different indexes.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -