SQL Memory Error Collector - how to enable.

Apr 14, 2014 at 11:12 PM
Hi,
There are a number of reports that are not available in SQL Nexus 4.0.0.64
  • Query Execution Memory
  • Memory Clerks
  • Workingset Trimming
    The required collector is listed as 'SQL Memory Error Collector'
    In the reason why a report is unavailable, in reference to memory reports, it states :
    "Data was not captured. For example, most memory reports will require SQL Memory Error Collector to be enabled explicitly'.
Does someone know how to explicitly enable the SQL Memory Error Collector?
Apr 26, 2015 at 7:11 PM
Edited Apr 26, 2015 at 7:11 PM
I have the same problem, not all the reports are showing up under SQL Perf Main. Here is the list that I don't see:
  1. Read Trace Reports
  2. Virtual File Stats
  3. Query Execution Memory
  4. Memory Clerks
  5. Workingset Triming
Any idea why I'm not seeing these reports?

Thanks,
BG
Coordinator
May 7, 2015 at 9:08 AM
ReadTrace reports are visible only if profiler traces are imported into the database. The other reports are available if you have data in the following tables:
2.Virtual File Stats - tbl_FileStats
3.Query Execution Memory - tbl_Query_Execution_Memory
4.Memory Clerks - tbl_DM_OS_MEMORY_CLERKS (Only if memory related DMV data was collected by the SQLDiag/PSSDiag data collection)
5.Workingset Triming - tbl_workingset_trimming
May 7, 2015 at 1:15 PM
Thanks for the reply Amitban. My question is how do I load the data into these tables because the data isn't collecting any trace files. Also on import when I point it to the folder where .trc files are located that I've collected from SQL Traces it doesn't load those files into SQL Nexus Tool.

So, I need some serious help to use this tool.

Thanks,

Aijaz Qureshi
Tel: (416) 879-1956