This project is read-only.

SQLNexus is not displaying the reports after import the sql diag data



I could not see the reports in reports section [i.e left side of the sql nexus tool screen] after importing the sql diag data.

I am using SqlNexus4.0.0.64 tool to import the SQL 2008 R2 captured scripts.

The reports section is displaying only [Instructions] and [SQL Perf Main] reports.

Appreciate your help.

Raj Kumar

file attachments


amitban wrote Jul 8, 2014 at 3:20 AM

The reports are available by clicking on SQL Perf Main. If the data is available to show the report from the imported data, then a drill through report link will be available on SQL Perf Main report page.

wrote Jul 8, 2014 at 8:49 AM

SPRaj wrote Jul 8, 2014 at 8:49 AM

Thank you Amitban for quick response.

I can see the reports by category in when I click on [sql perf main] in reports section. The reports are appearing on right side of the screen with blue color but when i click on the report e.g. bottleneck analysis nothing is happening. When I mouse over the report in blue color, the link is not changing to hand and when I click nothing is happening.

Please refer the attached screen shot.

Raj Kumar

SPRaj wrote Jul 10, 2014 at 5:49 AM

Hi Amit,

Appreciate your help.

Is there any workaround on above issue to display the reports.

Raj Kumar

amitban wrote Jul 14, 2014 at 7:13 AM

Capture a profiler trace to see if the stored procedures are being executed to return the results for the report. Also what is the size of your SQL Nexus database? The bottleneck analysis and wait statistics report rely on the *_SQL_200x_Perf_Stats_Startup.OUT file.

lorrinferdinand wrote Aug 28, 2014 at 4:01 PM

I have the same issue. Nothing is happening in profiler when the "link" is clicked.
Is there a way to view where the winform thinks the report is?


georgejjxu wrote Sep 1, 2014 at 4:50 PM

Yes, I have same problem. Although some report items are in blue, but it didn't open the report after clicking one of items. I checked the import log and no any error was found.

wrote Sep 1, 2014 at 4:53 PM

kbabudba wrote Sep 23, 2014 at 2:03 AM

I was able to fix this issue by installing "Update for Microsoft Visual Studio 2010 Service Pack 1 Report Viewer (KB2549864)" KB2549864