Finance | Project Operations, Human Resources, ...

Track down what SQL query is causing us to time out.

(0) Share

Report

Posted on by Riddleyw

We're currently running Microsoft Dynamics SL. After going through weeks of very sluggish (to the point of crashing) performance it was determined that some SQL query is taking up to 17 seconds and when called is called thousands of times in a row. I'm told that there is no way to determine what module is calling that code. Is that true? Anything I can look at? Thanks.

All responses (2)

Answers (0)

Suggested answer

CFROTON 4,710 on at

Like (0)

Report

RE: Track down what SQL query is causing us to time out.

Hello,

Sql server profiler found under SSMS tools menu will help you identify long running queries and errors, Support has several templates you can use and we frequently send them to partners for support cases of this nature. Unfortunately there is not a way to attach our profiler templates to the forums. You would need to create a support case to get the templates directly from support.
Erich Strelow F 1,642 on at

Like (0)

Report

RE: Track down what SQL query is causing us to time out.

The bread and butter for any SQL guru is the SQL Server Profiler. Since you already know about the offending query, it's likely you already have some output of the SQL Profiler. If the offending query is from the SL application, the same Profiler provides information about the user involved, the SQL query itself, and the connection information (workstation, network addressing, etc).

The bad scenario might happen if the offending SQL is somehow triggered by the SQL database itself. In that case, the link to the user-module-workstation is blurred. This can happen if there is some add-on in the SQL server itself, as in a replication engine, an auditing tool, a migration engine, a data synchronization engine. You might try to find out additional info on the Profiler results.