Share via

Microsoft SQL Server 2008 - Command Timeout

Anonymous
2017-09-05T14:28:05+00:00

We have a powerbuilder application which connects to SQL Server 2008 database. We have some reports which run around 3-4 hours. This is via a procedure invoked from the application code. when this long report runs, the application is getting disconnected from the database after 1 hour 40 minutes.

We have the below timeout parameters set in the connection string from application:

Connect timeout = 6000, TimeOut = 6000,CommandTimeOut = 6000

When we increased the CommandTimeOut Parameter to a higher value, the reports were completed with out database disconnect. But the performance was reduced. ie the reports are taking more time when we increased the value of CommandTimeout parameter in the connection string.

Could you please let me know what is the best solution for this issue.

***Post moved by the moderator to the appropriate forum category.***

Windows for home | Other | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2017-09-06T07:42:55+00:00

Hi Shiras,

Your Microsoft SQL Server 2008 question is more complex than what is typically answered here in Microsoft Answers forums. It is better suited for the IT Pro audience on TechNet. Kindly post your question in the TechNet Microsoft SQL forum.

For further queries, feel free to post back.

Was this answer helpful?

0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2017-09-06T11:42:34+00:00

    I have posted it on TechNet. Thank you.

    Was this answer helpful?

    0 comments No comments